Closed Ernestopheles closed 1 year ago
Having started docker-compose pull once more, I get this result (3 modules not pulled)
I think it is due to whatever is defined in your docker-compose.override.yml
Thanks, @cytopia, this helps me to avoid old unwanted PHP versions, I deleted them from the override.yml.
But still I need two runs of docker-compose pull:
Expected behaviour docker-compose pull pulls only versions not commented out in .env
docker-compose pull
pulls exactly what you specify to pull. If you have versions defined in override they will be pulled as well. You can also pull specific images via docker-compose pull <image>
.
Not sure why u have to pull twice?
Not sure why u have to pull twice?
First run seems unfinished (first 2 modules without a done
)
This behaviour did not appear any more, maybe as I changed to Docker Desktop. I think we can close this issue
Have you already looked into this bug?
(Optional) Error message
none
What went wrong?
docker-compose pull pulls also versions commented out in .env
Even beaks before having pulles all...
Expected behaviour
docker-compose pull pulls only versions not commented out in .env
How can we reproduce the bug?
do docker-compose pull in devilbox/
Host Operating System
Linux
Host Platform (amd64, arm64, other)
amd64
(Linux only) Is SELinux enabled?
Yes, SELinux is enabled
Docker version
Docker version 20.10.12, build e91ed57
Docker Compose version
docker-compose version 1.29.2, build 5becea4c
Devilbox version
Devilbox v3.0.0-beta-0.3 (2023-01-02)
Have you removed stopped containers before starting?
Yes
Have you pulled latest Docker images before starting?
Yes
Devilbox start command
docker-compose up -d httpd php mysql
Config: .env file
Config: docker-compose.override.yml
Config: ./check-config.sh
Log: docker-compose logs
(Optional) Additional information
Maybe has to do with my configuration, as I have a symlink of .env in devilbox/ and the .env original in another place
shortened .env in this issue as otherw3ise error body is too long appears