What's new
PGBlitz.com

Register Now! Find useful tips, Interact /w Community Members and join the part the Best Community on the Internet!

Discussion Docker/Portainer Error: "container already exists" when starting container

Status
Not open for further replies.

designgears

Full Member
Staff
I've seen this a few times now, usually after docker updates, very simple way to fix it, get the container id and run this command and everything will be back to normal :D

docker-containerd-ctr --address /run/docker/containerd/docker-containerd.sock --namespace moby c rm <containerd id>
 

Admin9705

Administrator
Project Manager
I've seen this a few times now, usually after docker updates, very simple way to fix it, get the container id and run this command and everything will be back to normal :D

docker-containerd-ctr --address /run/docker/containerd/docker-containerd.sock --namespace moby c rm <containerd id>
sorry @designgear little confused about what your posting :D
 

designgears

Full Member
Staff
haven't gotten this, but had this happen for something before. what is the actually causes? have to delete it out?
It doesn't delete anything, just removes the container from moby, no data lose or anything, just start the container afterwards.
 
Assists Greatly with Development Costs
Status
Not open for further replies.

Development Donations

 

Top NZB NewsGroups!

Members - Up To a 58% Discount!

Trending

Online statistics

Members online
12
Guests online
92
Total visitors
104
Top