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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
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