Closed thexpand closed 4 years ago
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.
The problem seems be solved with https://github.com/laminas/getlaminas.org/pull/7
Since we're no longer using Swoole to deploy the site, this is a moot issue.
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 runningdocker-compose up
. Thedocker-compose.yml
file defines a volume for all files within the root directory: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 thezend-expressive-swoole start
binary, which is located in thevendor
directory, resulting in the following error: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 thecomposer.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.