It sounds like you are using a volume and it's reading the settings you saved. What is the command you ran exactly and I can probably tell you what you need to change or delete to get rid of your old settings.
this post was submitted on 10 Feb 2024
20 points (95.5% liked)
Selfhosted
39386 readers
177 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:
- 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
rm the container, then run docker system prune -a. This will remove all unused docker images, containers, networks, volumes, etc.
Don't quote me on this, but I think you'd have to add --volumes
Didn’t end up needing to add —volumes. -a did the trick.
Betting that -a includes --volumes. 👍
Correct. The -a stands for all
Thanks, this worked perfectly!
Glad to help :)
You should perhaps skim through https://docs.docker.com/storage/ quickly. That document explains that docker containers only have very limited persistence (this is kind of the whole point of containers). The only persistence of note is volumes. This is normally how settings are saved between recreating containers.
As for dependencies, well it's possible that one container depends on the service of another. Perhaps this is what you are describing?
Either way, for more detailed help, you will have to explain your setup with more specific technical details.
docker rm removes the container and everything inside it.
If you have any bind mounts or volumes with settings stored in there, you'll need to remove those as well.
If you want to clear out any stopped containers, orphaned images, networks, etc run "docker system prune"
What I think is happening is there is a persistent volume mount that needs to be cleared out. If you're using the docker run command with a -v flag, check the host path. It's likely there are saved configurations you're passing into the container.
What command are you using to create the container?