this post was submitted on 10 Feb 2024
21 points (100.0% liked)

Selfhosted

40198 readers
1050 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I’m using tessypowder/backblaze-personal-wine, and I need to reinstall it due to some drive changes. I have tried docker rm [container ID], but when I add the container again, it seems to be stuck with the old wine settings. I have also tried adding it with a new name so it would theoretically be a totally new container, but that also seemed to inherit the broken wine settings.

I noticed that when I first install a container, there is a long ID string that seems to represent the container along with all the dependencies, but when I use docker ps, it only shows me a shorter string that seems to represent Backblaze alone. Should I be using rm with the longer string to remove wine too? If so, how can I get the terminal to display the full ID again so I can accomplish a full removal?

tl;dr How can I do a full removal of a docker container an all sub-programs (such as wine) that were installed along with it?

you are viewing a single comment's thread
view the rest of the comments
[–] danafest@lemm.ee 3 points 9 months ago

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.