-
Notifications
You must be signed in to change notification settings - Fork 54
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
unable to bind 80 and 443 inside container #32
Comments
Hi @joshuacox .... where are you running your dockers?? are you running your docker daemon with selinux enabled?? At some circumstances seems that docker with selinux makes that setcap doesn't work correctly.
I've just launched last version in my test system, from catalog listening at 80 and 443...It's working without any problem....
|
My dockers are in a rancher/cattle environment rancher 1.5.7 rancherOS 1.0.1 EDIT: adding the setcap output as traefik user in alpine-traefik container:
and for kicks as root on the host rancherOS
I don't think selinux is setup on rancher by default |
@rawmind0 is it possible that my binding in of |
Are you mounting /opt/traefik as a volume?? If so..don't do that..please, try deploying unmodified catalog package...or without additional volumes... You couldn't run setcap inside the container, due to is running as unprivileged user. Setcap is already done in docker build. :) |
If I put the latest 1.2.3 alpine on port 80 and 443 instead of 8080 and 8443 I get permission denied errors:
and if I leave http on port 8080 443 dies
you can see me wrestling with the issue here
The text was updated successfully, but these errors were encountered: