Replies: 14 comments
-
Only thing I can think of is that the you don't have permission to read |
Beta Was this translation helpful? Give feedback.
-
I have the same problem.
I have found that when disabling SELinux, the problem is gone. |
Beta Was this translation helpful? Give feedback.
-
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:
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Docker 1.3 now has a |
Beta Was this translation helpful? Give feedback.
-
Was there any luck in solving this? |
Beta Was this translation helpful? Give feedback.
-
I found the option that works well on my environment: |
Beta Was this translation helpful? Give feedback.
-
@sigelinde Yes, it pass the step, now I've got another problem, but it's not the same! |
Beta Was this translation helpful? Give feedback.
-
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:
|
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
This is working for me as well, thanks! (I am on a Fedora 29, freshly installed.) Maybe it could be documented somewhere? |
Beta Was this translation helpful? Give feedback.
-
Also fixes the issue on Fedora CoreOS 32. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Adding services:
nginx-proxy:
image: nginxproxy/nginx-proxy
security_opt:
- label:type:docker_t
. . . That does the trick for me running official Docker on RHEL 9 derivatives. |
Beta Was this translation helpful? Give feedback.
-
docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock jwilder/nginx-proxy
yields the following error (from
docker logs
)Beta Was this translation helpful? Give feedback.
All reactions