Bom dia, hoje é décimo dia de tentativa, cheguei a postar no github, mas acho que as issues lá, não são ativas. Então venho tentar o apoio por aqui. Desde já agradeço qualquer comentário.
VERSÃO:
1.3.6.
DESCRIÇÃO:
Ao tentar instalar o i-diario, via DOCKER, ele finaliza com essa mensagem de erro:
diario | from /app/bin/rails:9:in `require'
idiario | from /app/bin/rails:9:in `<top (required)>'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
idiario | from /box/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
idiario | from /box/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
idiario | from /box/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
idiario | from /box/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
idiario | from /app/bin/spring:15:in `require'
idiario | from /app/bin/spring:15:in `<top (required)>'
idiario | from bin/rails:3:in `load'
idiario | from bin/rails:3:in `<main>'
idiario exited with code 1
OBSERVAÇÕES:
No linux meu docker --version
Docker version 20.10.9, build c2ea9bc
AMBIENTE:
- Plataforma utilizada (p.ex. Docker, instalação direta): DOCKER
- Sistema operacional e versão (p.ex. Ubuntu 16.04, Windows 7): Manjaro
- Navegador e versão (p.ex. Chrome 35.9.9.9): Chrome 100
- Outros detalhes importantes: Pasta com permissões adequadas.
https://github.com/portabilis/i-diario/issues/98
É importante você trazer todo erro.
Obrigado pelo retorno Tiago.
❯ docker-compose up --build
[+] Building 0.9s (10/10) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/ruby:2.4.10-slim-buster 0.9s
=> [1/6] FROM docker.io/library/ruby:2.4.10-slim-buster@sha256:ac34ee3f02c12e9c6fdfa2164bd7f98e579 0.0s
=> CACHED [2/6] RUN apt-get update -qq 0.0s
=> CACHED [3/6] RUN apt-get install -y build-essential libpq-dev nodejs npm git 0.0s
=> CACHED [4/6] RUN npm i -g yarn 0.0s
=> CACHED [5/6] RUN mkdir /app 0.0s
=> CACHED [6/6] WORKDIR /app 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:dde936a036588a9b977c548da02026f20168ee8ccf0af5820f144d2773646882 0.0s
=> => naming to docker.io/library/i-diario_app 0.0s
[+] Running 4/0
⠿ Network i-diario_default Created 0.0s
⠿ Container redis-idiario Created 0.0s
⠿ Container postgres-idiario Created 0.0s
⠿ Container idiario Created 0.0s
Attaching to idiario, postgres-idiario, redis-idiario
redis-idiario | 1:C 29 Apr 12:02:35.142 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-idiario | 1:C 29 Apr 12:02:35.142 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=1, just started
redis-idiario | 1:C 29 Apr 12:02:35.142 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis-idiario | 1:M 29 Apr 12:02:35.143 * Running mode=standalone, port=6379.
redis-idiario | 1:M 29 Apr 12:02:35.143 # Server initialized
redis-idiario | 1:M 29 Apr 12:02:35.143 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-idiario | 1:M 29 Apr 12:02:35.143 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis-idiario | 1:M 29 Apr 12:02:35.143 * Ready to accept connections
postgres-idiario |
postgres-idiario | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres-idiario |
postgres-idiario | 2022-04-29 12:02:35.192 UTC [1] LOG: starting PostgreSQL 12.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
postgres-idiario | 2022-04-29 12:02:35.192 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres-idiario | 2022-04-29 12:02:35.192 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres-idiario | 2022-04-29 12:02:35.196 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-idiario | 2022-04-29 12:02:35.206 UTC [21] LOG: database system was shut down at 2022-04-29 12:02:26 UTC
postgres-idiario | 2022-04-29 12:02:35.209 UTC [1] LOG: database system is ready to accept connections
idiario | The Gemfile's dependencies are satisfied
idiario | yarn install v1.22.18
idiario | [1/4] Resolving packages...
idiario | success Already up-to-date.
idiario | Done in 0.33s.
idiario | Starting..
idiario | /box/gems/skylight-core-4.3.2/lib/skylight/core/probes.rb:118:in `require': /box/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/storage/redis_store.rb:238: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
idiario | rescue
idiario | ^
idiario | /box/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/storage/redis_store.rb:352: syntax error, unexpected keyword_end, expecting end-of-input
idiario | from /box/gems/skylight-core-4.3.2/lib/skylight/core/probes.rb:118:in `require'
idiario | from /box/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `block in require'
idiario | from /box/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:240:in `load_dependency'
idiario | from /box/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `require'
idiario | from /box/gems/rack-mini-profiler-3.0.0/lib/rack-mini-profiler.rb:21:in `<top (required)>'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:81:in `require'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:81:in `block (2 levels) in require'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `each'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `block in require'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `each'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `require'
idiario | from /usr/local/lib/ruby/site_ruby/2.4.0/bundler.rb:114:in `require'
idiario | from /app/config/application.rb:8:in `<top (required)>'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:78:in `require'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:78:in `block in server'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in `tap'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in `server'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
idiario | from /box/gems/railties-4.2.11.1/lib/rails/commands.rb:17:in `<top (required)>'
idiario | from /app/bin/rails:9:in `require'
idiario | from /app/bin/rails:9:in `<top (required)>'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
idiario | from /box/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
idiario | from /box/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
idiario | from /box/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
idiario | from /box/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
idiario | from /box/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
idiario | from /app/bin/spring:15:in `require'
idiario | from /app/bin/spring:15:in `<top (required)>'
idiario | from bin/rails:3:in `load'
idiario | from bin/rails:3:in `<main>'
idiario exited with code 1
@hermesalvesbr veja se na versão 1.4.0 o problema não está resolvido.
1 curtida
Bom dia Eder, obrigado por responder. O erro foi resolvido, o problema agora é outro.
Informei com riqueza de detalhes em: Docker install: idiario exited with code 1 · Issue #98 · portabilis/i-diario · GitHub