-
Notifications
You must be signed in to change notification settings - Fork 78
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
You cannot link containers when using net=host #8
Comments
I tested with a freshly build image and the registry downloaded image, using docker 1.4.1
|
Thank you for response This is the way Im running your solution on my Vagrant machine: docker run -d -name=squid --net=host --privileged -e DISK_CACHE_SIZE=5000 -e MAX_CACHE_OBJECT=1000 squid docker run --name=iptables --privileged --net=host iptables After that Im trying to build my image without setting http_proxy inside Docker file : Docker file FROM centos:6.5 Thanks. |
I can run your docker file executing the following: Note: I ran the iptables with -ti not -d to be able to see the console output and so I can ctrl-c it to clean up the iptables on shutdown. With the above run I could build the following dockerfile:
What does your iptables look like for you when running? This is mine.
|
TCP_MISS_ABORTED/000 0 GET http://ftp.freepark.org/pub/linux/distributions/centos/6.6/updates/x86_64/Packages/bind-libs-9.8.2-0.30.rc1.el6_6.1.x86_64.rpm
In case I set env http_proxy inside container It works like a charm.
Thanks,
The text was updated successfully, but these errors were encountered: