docker-compose up fails #25

Activity

1. AntoninSlejska commented on Sep 25, 2018

   

   AntoninSlejska

   on Sep 25, 2018

   Last edited by AntoninSlejska

   More actions

   I have the same problem (Docker version: 18.06.1-ce-win73 (19507)):

   $ docker-compose up
   Creating network "contenta_docker_contenta" with the default driver
   Creating volume "contenta_docker_data" with default driver
   Creating contenta_docker_database_1 ... done
   Creating contenta_docker_php_1      ... done
   Creating contenta_docker_nginx_1    ... done
   Attaching to contenta_docker_database_1, contenta_docker_php_1, contenta_docker_nginx_1
   database_1  | standard_init_linux.go:190: exec user process caused "no such file or directory"
   php_1       | standard_init_linux.go:190: exec user process caused "no such file or directory"
   nginx_1     | nginx: [emerg] host not found in upstream "php" in /etc/nginx/sites/drupal.conf:62
   contenta_docker_database_1 exited with code 1
   contenta_docker_php_1 exited with code 1
   contenta_docker_nginx_1 exited with code 1
   
2. AntoninSlejska commented on Oct 8, 2018

   

   AntoninSlejska

   on Oct 8, 2018

   Last edited by AntoninSlejska

   More actions

   My colleague Jörg have tried to delete everything:

   docker system prune -a
   

   Then he started from null, but set the Git configuration autoclrf to 'input':

   git clone https://github.com/contentacms/contenta_docker.git --config core.autocrlf=input
   cd contenta_docker
   docker-compose build
   ...
   

   It worked by him. I have tried it as well, and the Contenta CMS works by me now.
3. pcambra commented on Oct 8, 2018

   

   pcambra

   on Oct 8, 2018

   Member

   More actions

   Maybe prune is a bit drastic, but removing the volumes and containers to ensure everything is rebuilt? or --force-recreate in the docker-compose would work as well?
4. AntoninSlejska commented on Oct 8, 2018

   

   AntoninSlejska

   on Oct 8, 2018

   More actions

   @pcambra I suppose it should be sufficient. The crucial measure, which has to be taken, is: 'git clone ... --config core.autocrlf=input'.
5. pcambra commented on Sep 18, 2019

   

   pcambra

   on Sep 18, 2019

   Member

   More actions

   I got why this is failing, this is part of what I mentioned on #21 about making the install more robust.

   What was happening is that the php container was failing due composer not being able to run install on a non-empty folder and thus nginx cannot start.

   This commit should make it a bit better b45bcd2

   It'd be great if someone would confirm this is fixed or we need to keep digging.