Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to create Docker container from built image #4

Closed
thexpand opened this issue Apr 19, 2019 · 3 comments

Comments

@thexpand
Copy link
Contributor

@thexpand thexpand commented Apr 19, 2019

The image builds flawlessly. However, creating a container from the built image fails. This happens, because of the volume mapping and the missing vendor directory after running docker-compose up. The docker-compose.yml file defines a volume for all files within the root directory:

    volumes:
      - .:/var/www

When in development, this overwrites the contents of the image, thus removing the vendor directory. On the other hand, the entry point file tries to start swoole by running the zend-expressive-swoole start binary, which is located in the vendor directory, resulting in the following error:

php_1 | Could not open input file: vendor/bin/zend-expressive-swoole
getlaminasorg_php_1 exited with code 1

This could be resolved by running composer install on the local machine, but that doesn't seem right. The machine might not meet the dependencies in the composer.json, so it's not an option.

We should think of a way on how to avoid this.

UPDATE: The same issue is valid for the assets in public/css. They get overwritten by the volume mount.

@dominicdettabp

This comment has been minimized.

Copy link

@dominicdettabp dominicdettabp commented Apr 29, 2019

This is the exact problem I experienced while executing docker-compose up.
I tried to execute manually composer install but obviously I received a bunch of error associated with ext-swoole not installed. I'm stuck.

@bu3tt1

This comment has been minimized.

Copy link
Contributor

@bu3tt1 bu3tt1 commented Apr 30, 2019

The problem seems be solved with #7

@weierophinney

This comment has been minimized.

Copy link
Member

@weierophinney weierophinney commented Nov 8, 2019

Since we're no longer using Swoole to deploy the site, this is a moot issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.