[Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4
Peter Korsgaard
peter at korsgaard.com
Sat Jan 11 08:31:16 UTC 2020
>>>>> "Christian" == Christian Stewart <christian at paral.in> writes:
> Hi Peter,
> On Fri, Jan 10, 2020 at 12:40 AM Peter Korsgaard <peter at korsgaard.com> wrote:
>> I was of the understanding that docker-proxy isn't really needed any
>> more. Can you clarify?
> I have build + run tested it with the latest version as built by this
> patch. Docker-proxy is still used in the Gentoo build files.
> There's not much information online about docker-proxy, one article
> even claims that it should be a symlink to the docker binary itself.
> The docker-proxy binary is executed when port-forwarding.
> $ docker run -d -p 80:8080 nginx
> Results in the following being run:
> /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80
> -container-ip 172.17.0.2 -container-port 8080
> The binary does need to be in place, and it works fine after this
> version bump. I'm not sure if it could be replaced with a symlink to
> the docker binary itself.
Ok. I am referring to references like this:
https://github.com/moby/moby/issues/14856
https://serverfault.com/questions/633604/what-is-the-point-of-the-docker-proxy-process-why-is-a-userspace-tcp-proxy-need
Which makes me think that docker-proxy should be optional rather than
unconditionally selected by docker-engine.
What do you think?
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list