New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker socket doesn't have to be writeable to resolve container names #6508
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small changes requested.
Also, let's consider how this connects to #6441. Working on the same part of the same file here. |
Yea... My diff takes out the GID logic in the run script. I had originally added some logic to just update the |
Ok. Got something workable based on what you have suggested. 👍 I'll try to roll this updated documentation into my diff. |
Co-Authored-By: Joel Hans <joel.g.hans@gmail.com>
Co-Authored-By: Joel Hans <joel.g.hans@gmail.com>
Actually, this information already exists on the current version of the README. Apologies for the delay @tobiasmuehl !!! |
Summary
Documentation tells users to bind docker socket writeable, although it doesn't seem necessary for docker container name resolution.
Component Name
Gitbook
Additional Information
Other users reporting success with this method can be found in this issue thread