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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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 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.
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