All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4
Date: Tue, 04 Feb 2020 15:06:11 -0800	[thread overview]
Message-ID: <871rragdgc.fsf@paral.in> (raw)
In-Reply-To: <87eew6jsx7.fsf@dell.be.48ers.dk>

Hi Peter,

Peter Korsgaard <peter@korsgaard.com> writes:
> 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?

We could set --userland-proxy=false on the daemon, perhaps, and remove
the docker-proxy requirement? I will do some tests on this.

I think it makes sense to first bump docker-proxy (it still is started
and used with the current configuration) and then remove it later.

Best regards,
Christian

  reply	other threads:[~2020-02-04 23:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10  4:50 [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Christian Stewart
2020-01-10  4:50 ` [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4 Christian Stewart
2020-01-10  8:40   ` Peter Korsgaard
2020-01-11  4:20     ` Christian Stewart
2020-01-11  8:31       ` Peter Korsgaard
2020-02-04 23:06         ` Christian Stewart [this message]
2020-01-10  8:39 ` [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Peter Korsgaard
2020-01-11  4:21   ` Christian Stewart
2020-02-04 23:02     ` Christian Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rragdgc.fsf@paral.in \
    --to=christian@paral.in \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.