Selfhosted

40113 readers

1425 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

[email protected]

[Solved] Docker Compose Issue with Stale Data on Startup (rollenspiel.forum)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

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 [container]; docker rm [container]) if not using docker compose down . If you don't remove the container, it will keep using the old image.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

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. thanks for the help