Selfhosted

39964 readers

246 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]

Docker container reappears constantly after "rm" or "rm -f" (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

Hello everyone,

I have containers that I want to get rid of because I can't make them work, but I can't seem to get rid of them. I'm using Portainer usually and the remove command on the container works, but they shortly reappear as newly created containers.

I moved to the terminal to try and sudo it out of existence manually, docker ps, the containers are here. So I sudo docker stop , the terminal confirms. Then sudo rm -f , confirmed again.

Docker ps shows they are gone, but a minute later another docker ps shows they are back up again.

I've looked it up online and people mentioned it might be running as a service. The command "docker service ls" returns an empty list.

How can I nuke those containers?

top 5 comments

sorted by: hot top controversial new old

[–] [email protected] 21 points 1 year ago

are you using kube? or docker-compose?

of you are using docker compose, and in the compose file there is restart: always the container will be restarted if it disappears.

to remove it do docker compose down

[–] [email protected] 7 points 1 year ago

Like others have asked, how exactly did you create these containers? If they were through Portainer did you use a compose file in a stack or did you use the GUI the entire way?

This will nuke them assuming you don't have something recreating them.

docker ps -a # find your rogue container, copy the container id, my example is a0ff66a83c73
docker stop a0ff66a83c73
docker rm a0ff66a83c73

My suggestion is to go through the process you did to try to deploy them and clean it up from that direction.

[–] [email protected] 4 points 1 year ago

How did you create them?

[–] [email protected] 2 points 1 year ago

Are they part of a stack or docker-compose?