ezsystems / launchpad

CLI tool to bootstrap an eZ Platform project Docker stack | #justcode
https://ezsystems.github.io/launchpad
MIT License
22 stars 27 forks source link

Cannot start service nginx: OCI runtime create failed #35

Closed jankal closed 6 years ago

jankal commented 6 years ago
Q A
Bug report? yes
Feature request? no
BC Break report? no
RFC? no
Version 614ccf2e410ae6797a5049395aaa3978c2e96ee4
Environment Windows
jankal@ajank  /c/Users/alexa/Projekte/cyprotect-backend  ez init

               *
       *             *
                    ___
              |     | |
    *        / \    | |
            |--o|===|-|
            |---|   | |
       *   /     \  | |
          |  eZ   | | |
          |       |=| |
          Launchpad | |
          |_______| |_|
           |@| |@|  | |
  ____\|/___________|_|_

    eZ Launchpad 614ccf2e410ae6797a5049395aaa3978c2e96ee4

 eZ Launchpad will install a new architecture for you.
 Three modes are available:
  - standard: All the services, no composer auth
  - standard-with-composer-auth: Standard with ability to provide Composer Auth, useful for eZ Platform Enterprise
  - expert: All the questions will be asked and you can select the services you want only
 Please select your Initialization mode [standard]:
  [0] standard
  [1] standard-with-composer-auth
  [2] expert
 > 0

Building engine
Step 1/6 : FROM plopix/docker-php-ez-engine:7
 ---> e88b0ebccaa8
Step 2/6 : MAINTAINER Plopix
 ---> Running in 8d53a5fd9e35
Removing intermediate container 8d53a5fd9e35
 ---> 8dad2d0c663a
Step 3/6 : COPY entrypoint.bash /entrypoint.bash
 ---> 5b3917d15f94
Step 4/6 : RUN chmod +x /entrypoint.bash
 ---> Running in b5042d7e6aeb
Removing intermediate container b5042d7e6aeb
 ---> c38b37d03665
Step 5/6 : ENTRYPOINT ["/entrypoint.bash"]
 ---> Running in 03bcd5373afa
Removing intermediate container 03bcd5373afa
 ---> ade3795a6702
Step 6/6 : CMD ["php-fpm"]
 ---> Running in fef0ee07a32e
Removing intermediate container fef0ee07a32e
 ---> 9a3ba7af8d32
Successfully built 9a3ba7af8d32
Successfully tagged jankalcyprotectbackend_engine:latest
db uses an image, skipping
Recreating jankalcyprotectbackend_engine_1 ... done
Starting jankalcyprotectbackend_db_1       ... done

Installation Composer in the container
All settings correct for using Composer
Downloading...

Composer (version 1.6.5) successfully installed to: /var/www/html/project/composer.phar
Use it: php composer.phar

Installation eZ Platform (ezsystems/ezplatform:2.*:clean) in the container

  [ErrorException]
  include(phar:///var/www/html/project/composer.phar/vendor/composer/../../src/Composer/Command/SuggestsCommand.php): failed to o
  pen stream: phar error: Cannot open phar archive "/var/www/html/project/composer.phar" for reading

/var/www/html/project/ez_install.bash: line 16: cd: ezplatform: Not a directory
rm: cannot remove '.env': No such file or directory
rm: cannot remove '.platform.app.yaml': No such file or directory
rm: cannot remove 'Dockerfile': No such file or directory
rm: cannot remove '.travis.yml': No such file or directory
mysqld is alive

Could not open input file: bin/console
Could not open input file: bin/console
Installation OK
/var/www/html/project/ez_install_solr.bash: line 12: cd: /var/www/html/project/ezplatform: Not a directory
cp: cannot stat 'vendor/ezsystems/ezplatform-solr-search-engine/lib/Resources/config/solr/*': No such file or directory
Removing jankalcyprotectbackend_nginx_1
Starting jankalcyprotectbackend_mailcatcher_1 ...
Starting jankalcyprotectbackend_mailcatcher_1 ... done
Starting jankalcyprotectbackend_adminer_1     ... done
Starting jankalcyprotectbackend_redisadmin_1  ... done
Recreating jankalcyprotectbackend_engine_1    ... done
Starting jankalcyprotectbackend_blackfire_1   ... done
Recreating jankalcyprotectbackend_redis_1     ...
Recreating de8b6aae1a7f_jankalcyprotectbackend_nginx_1 ... error
Recreating jankalcyprotectbackend_solr_1               ...

ERROR: for de8b6aae1a7f_jankalcyprotectbackend_nginx_1  Cannot start service nginx: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/host_mnt/c/Users/alexa/Projekte/cyprotect-backend/ezplatform/doc/nginx/ez_params.d\\\" to rootfs \\\"/var/lib/docker/overlay2/07aba98117b97b26cacfRecreating jankalcyprotectbackend_redis_1              ... doneojekte/cyprotect-backend/ezplatform/doc/nginx/ez_params.d: not a directory\\\"\"": unknown: Are you trying to mount a directory ontoRecreating jankalcyprotectbackend_solr_1               ... done

ERROR: for nginx  Cannot start service nginx: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/host_mnt/c/Users/alexa/Projekte/cyprotect-backend/ezplatform/doc/nginx/ez_params.d\\\" to rootfs \\\"/var/lib/docker/overlay2/07aba98117b97b26cacfd13e197ba0cfb50c55ac17c11f9304d19a0efd36e0ad/merged\\\" at \\\"/etc/nginx/ez_params.d\\\" caused \\\"stat /host_mnt/c/Users/alexa/Projekte/cyprotect-backend/ezplatform/doc/nginx/ez_params.d: not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the
specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

In Process.php line 239:

  The command "docker-compose -p jankalcyprotectbackend -f /c/Users/alexa/Projekte/cyprotect-backend/provisioning/dev/docker-comp
  ose.yml up -d" failed.

  Exit Code: 1(General error)

  Working directory: /c/Users/alexa/Projekte/cyprotect-backend

  Output:
  ================

  Error Output:
  ================

docker:initialize [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-c|--config CONFIG] [--] <command> [<repository>] [<version>] [<initialdata>]
Plopix commented 6 years ago

Hello thanks for this issue. eZ Launchpad is sadly not working on Windows due to how work Docker on Windows. (WSL, permissions, performances, etc. etc.) It is not usable :/

Best approach if you are staying on WIndows is to have a local or remove Linux box on which you would install Docker and Docker Compose, plus a way to edit the code from your host to this box. (like a PHPStorm configuration to push a file after save, or sshfs etc. etc.)

I let you close the issue when you will have read that.

jankal commented 6 years ago

@Plopix Thank you.