Hello everyone,
I’m sure there are a few people here who are fitter in #DockerCompose than I am. Currently I have the problem that when starting the docker-compose the latest data is probably not used although the local copy of the repo is up to date.
Does anyone have an idea?
https://codeberg.org/grindhold/flohmarkt/src/branch/master/docker-compose_prod.yaml
I came across the problem because of this issue and that it is not up to date because of this issue.
You must log in or register to comment.
Have you tried clearing build cache? That docker compose has build init and web containers. Latest version docker compose have —no-cache option
https://docs.docker.com/engine/reference/commandline/compose_build/
There is also prune command
https://docs.docker.com/engine/reference/commandline/builder_prune/
thanks for the help, that put me on the right track, apparently an old image was used.
By data do you mean image?
If so, make sure you run a
docker compose buildafter pulling the repo, and also make sure you stop and remove the container. (docker stop [container]; docker rm [container]) if not usingdocker compose down. If you don’t remove the container, it will keep using the old image.I always thought that a
docker-compose up -dalso builds a new image. But apparently I have to rundocker-compose up --build -d. thanks for the help
