-
Notifications
You must be signed in to change notification settings - Fork 3k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Bad endpoint: stat /tmp/docker.sock: permission denied #40
Comments
Only thing I can think of is that the you don't have permission to read |
I have the same problem.
I have found that when disabling SELinux, the problem is gone. |
Did any of the suggestions I mentioned earlier help? Another idea might be to try and mount docker.sock to a different location w/ something like:
|
No, It doesn't.
The container is running (instead of stoping), but looping on the connection error. After some research, I can say that this is with no doubt a SELinux problem, using
Maybe a specific SELinux policy or a command may correct this, but I'm not a SELinux expert... It's working, but we have to disable SELinux, which is not a good solution. |
Docker 1.3 now has a |
Was there any luck in solving this? |
I found the option that works well on my environment: |
@sigelinde Yes, it pass the step, now I've got another problem, but it's not the same! |
I've gotten this to work by adding a module to the SELinux policy. My current module is here: compile and add to policy with:
Should work, but if not, you can check why by running:
and you can generate a new module to insert that will allow the currently denied behavior with:
|
I have also had this issue. After much searching I found out that my username space was enabled and preventing my container from having docker.sock access. OS: Alpine |
This is working for me as well, thanks! (I am on a Fedora 29, freshly installed.) Maybe it could be documented somewhere? |
Also fixes the issue on Fedora CoreOS 32. |
Hoping to get some support on this issue. In my environment we're looking to run nginx-proxy with a non-root user account. I've cloned the nginx-proxy repository so that I could modify the dockerfile formy purposes (creating a non root user, chown'ing necessary directories, etc.) One area I am still stuck on is permissions to /tmp/docker.sock. I've attempted the various fixes already mentioned here but I believe my issue is slightly different in that I am attempting to run nginx-proxy with a non-root user. Does anybody know if it's possible to modify permissions on /tmp/docker.sock for a non-root user? I've attempted a few other things such as mounting the volume during my |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock jwilder/nginx-proxy
yields the following error (from
docker logs
)The text was updated successfully, but these errors were encountered: