Issue with routing dockers through another container


Recommended Posts

Typically, this works well for me.  However, if the routing container disappears then the web interfaces gets stuck in a loop of trying to rebuild all the dependent containers.  It never returns so that I can fix the underlying problem.

 

 The underlying issue is that when I updated glueTUN it disappeared and became an abandoned image.  So I need to re-install it.

 

I had to edit every dependent docker to no longer route through glueTUN, then apply and stop the docker.  I could then add glueTUN back and redo all the other dockers.

 

Is this how it is expected to work? 

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.