pac4cli cannot be used for building docker images about pac4cli HOT 3 CLOSED

Thanks for the detailed report @badp !

I don't know if you have a happy middle ground between just binding to localhost and binding to literally anything

One potential (stopgap) solution is to add a list of IP addresses to listen on to the configuration file. That would help provided that your host's ip address on docker0 is stable.

Slightly more advanced would be to query docker for its network configuration, and listen on the appropriate interface.

Even more advanced would be if docker were to support some sort of "sidecar" concept, where it starts a process (pac4cli -p 172.17.0.1:3128) whenever any container is running.

What do you think?

from pac4cli.

@badp could you test whether #34 (add-interface-option) works for you? Instructions:

git clone https://github.com/tkluck/pac4cli
cd pac4cli
git checkout add-interface-option
make env
env/bin/python main.py -s 172.17.0.1 -p 3128 &

and then see if your docker container can use it.

from pac4cli.

Hey @badp , just out of interest: did you also look into the --network host option to docker run? I just checked that that also allows the container to connect to the pac4cli instance on the host.

from pac4cli.