7
[Solved] Docker Compose Issue with Stale Data on Startup
(rollenspiel.forum)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Nov 2023
7 points (73.3% liked)
Selfhosted
40246 readers
537 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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