Can't access docker containers after kernel panic crash.


RadOD

Recommended Posts

After a kernel panic and crash which I suspect was related somehow to assigning custom IP addresses on BR0 similar what is described here...

 

Many dockers have nothing under the "port mappings" column even though they used to.  I cannot access any docker at all via http://IP:port even those that still list the IP:port mappings.  I am left with two 'versons' of BR:  

br-9c2cde536e88 and br-03ece3ee359d that I didn't create and cannot delete.

 

 

At this point, I am over my head and totally confused.  

 

Is there an easy way to wipe all the docker network setting and just start over from scratch?

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.