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
Localhost acl rule fails because docker push is using server ip not localhost #64
Comments
It sounds like all you need to do is add an acl to allow pushes from your server ip. So for example if you are logged into a server with the host "myserver.com" and running Or you could add entry into your server's /etc/hosts
|
Thanks @carsonoid. I would prefer not to do the first method in case the server ip changes. The second one looks good but still doesn't work for some reason. Without the "127.0.0.1 myserver.com" entry when I do a pull I get this in the log
With I now get this
It still doesn't work because "172.17.0.1" is not in a rule. Any ideas why it's now "172.17.0.1" not "127.0.0.1"? |
I'm really new to docker but googling looks like that might be the ip that the host has on dockers bridged network? |
Can someone confirm that in the having "127.0.0.1" in an acl actually can work? |
Ok yes so it looks like the default docker bridge network is what containers get put onto, which is basically a nat network, and the gateway ip on this network (ie the host) is 172.17.0.1. So I now have:
and it works! So my question now is should this be the ip in the default config, not 127.0.0.1? |
Any idea how to make
docker push
run with the source address "127.0.0.1"?The text was updated successfully, but these errors were encountered: