Docker Compose Issue with Stale Data on Startup

https://rollenspiel.forum/post/35826

Docker Compose Issue with Stale Data on Startup - RollenspielMonster

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 [https://codeberg.org/grindhold/flohmarkt/src/branch/master/docker-compose_prod.yaml]

Have you tried clearing build cache? That docker compose has build init container. Latest version docker compose have —no-cache option

docs.docker.com/engine/…/compose_build/

"docker compose build"

""

Docker Documentation
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 build after pulling the repo, and also make sure you stop and remove the container. (docker stop && docker rm if not using docker compose down . If you don’t remove the container, it will keep using the old image.

I always thought that a docker-compose up -d also builds a new image. But apparently I have to run docker-compose up --build -d.