From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sat, 11 Jan 2020 09:31:16 +0100 Subject: [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4 In-Reply-To: (Christian Stewart's message of "Fri, 10 Jan 2020 20:20:34 -0800") References: <20200110045033.1920685-1-christian@paral.in> <20200110045033.1920685-2-christian@paral.in> <87lfqfg0ve.fsf@dell.be.48ers.dk> Message-ID: <87eew6jsx7.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Christian" == Christian Stewart writes: > Hi Peter, > On Fri, Jan 10, 2020 at 12:40 AM Peter Korsgaard 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