All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Jansa" <Martin.Jansa@gmail.com>
To: "Yu, Mingli" <mingli.yu@windriver.com>
Cc: Joshua Watt <jpewhacker@gmail.com>,
	Scott Murray <scott.murray@konsulko.com>,
	 bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] prserv: make localhost work
Date: Wed, 1 Sep 2021 11:14:36 +0200	[thread overview]
Message-ID: <CA+chaQe2yEvPr9X86X-YYWypXhu4JHLM8TsHLpWpbfxPqQqe+g@mail.gmail.com> (raw)
In-Reply-To: <af883af8-192c-0550-76ea-ee5190ba54c1@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

>
>
> > I think that was because IPv6 support had been incorrectly configured
> > for Docker, perhaps that is the same thing happening in your setup?
>
> In the same docker, the PR service works with PRSERV_HOST =
> "localhost:0" before, but it begins not work recently after some code
> restructure for prserv part.
>
> BTW, the ipv6 is disabled in the docker of my env.
>

Check your /etc/hosts

There is ::1 localhost localhost-ip6 even when ipv6 is disabled in docker's
deamon.json.

And that makes bitbake (asyncio) to try binding to ::1 instead of
127.0.0.1, if you remove "localhost" from ::1 in /etc/hosts in running
container, then it works again OK.

My patch allows you to use 127.0.0.1:0 explicitly and still keep the same
behavior (as autostarted prserv with random port) as when localhost:0 is
being used (and also for consistency).

Your patch is IMHO good addition to that (that the localhost is resolved in
python and then people don't need to use 127.0.0.1 explicitly).

Regards,

[-- Attachment #2: Type: text/html, Size: 1423 bytes --]

      reply	other threads:[~2021-09-01  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16A04D855643B3E7.30479@lists.openembedded.org>
2021-08-31  7:48 ` [PATCH] prserv: make localhost work Yu, Mingli
2021-08-31 15:01   ` Scott Murray
2021-09-01  1:20     ` Yu, Mingli
2021-09-01  1:31       ` [bitbake-devel] " Joshua Watt
2021-09-01  1:51         ` Yu, Mingli
2021-09-01  9:14           ` Martin Jansa [this message]

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=CA+chaQe2yEvPr9X86X-YYWypXhu4JHLM8TsHLpWpbfxPqQqe+g@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=jpewhacker@gmail.com \
    --cc=mingli.yu@windriver.com \
    --cc=scott.murray@konsulko.com \
    /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.