Salut,
J’ai suivi la procédure d’installation Docker.
Mon fichier env est bien configuré, toutes les étapes se passent sans problèmes.
Par contre lors du lancement :
fabmanager_1 | 2020-01-29 20:46:03,304 INFO spawned: ‹ app › with pid 161
fabmanager_1 | 2020-01-29 20:46:04,305 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
fabmanager_1 | 2020-01-29 20:46:09,326 INFO exited: app (exit status 1; not expected)
fabmanager_1 | 2020-01-29 20:46:10,329 INFO spawned: ‹ app › with pid 170
fabmanager_1 | 2020-01-29 20:46:11,331 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
…
Le ficher app-stderr.log produit l’erreur suivante :
/usr/local/bundle/gems/puma-3.10.0/lib/puma/launcher.rb:342:in stat': No such file or directory @ rb_file_s_stat - /srv/fab (Errno::ENOENT) from /usr/local/bundle/gems/puma-3.10.0/lib/puma/launcher.rb:342:in generate_restart_data’
from /usr/local/bundle/gems/puma-3.10.0/lib/puma/launcher.rb:64:in initialize' from /usr/local/bundle/gems/puma-3.10.0/lib/rack/handler/puma.rb:65:in new’
from /usr/local/bundle/gems/puma-3.10.0/lib/rack/handler/puma.rb:65:in run' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:287:in start’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/server.rb:80:in start' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:80:in block in server’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in tap' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in server’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39:in run_command!' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands.rb:17:in <top (required)>’
from bin/rails:4:in require' from bin/rails:4:in ’
Auriez vous une piste ?
Dav’