From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [RFC PATCH] tests/docker: Allow passing --network option when building images
Date: Tue, 19 Jan 2021 14:20:30 +0000 [thread overview]
Message-ID: <20210119142030.GD2335568@redhat.com> (raw)
In-Reply-To: <f34c7ff5-cd02-83b4-d3d8-c2ec7ac4334f@amsat.org>
On Tue, Jan 19, 2021 at 02:40:13PM +0100, Philippe Mathieu-Daudé wrote:
> On 1/19/21 12:27 PM, Alex Bennée wrote:
> > Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> >
> >> When using the Docker engine, build fails because the container is
> >> unable to resolve hostnames:
> >>
> >> $ make docker-image-debian-s390x-cross NETWORK=host ENGINE=docker
> >> BUILD debian10
> >> #6 9.679 Err:1 http://deb.debian.org/debian buster InRelease
> >> #6 9.679 Temporary failure resolving 'deb.debian.org'
> >> #6 16.69 Err:2 http://security.debian.org/debian-security buster/updates InRelease
> >> #6 16.69 Temporary failure resolving 'security.debian.org'
> >> #6 22.69 Err:3 http://deb.debian.org/debian buster-updates InRelease
> >> #6 22.69 Temporary failure resolving 'deb.debian.org'
> >> #6 22.74 W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'deb.debian.org'
> >> #6 22.74 W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Temporary failure resolving 'security.debian.org'
> >> #6 22.74 W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'deb.debian.org'
> >> #6 22.74 W: Some index files failed to download. They have been
> >> ignored, or old ones used instead.
> >
> > I'm confused by this one as it currently works for me. That said I
> > thought the actual behaviour was meant to be networking is enabled by
> > default and explicitly disabled by the run step (which shouldn't be
> > pulling extra stuff down).
> >
> > This was last tweaked by Daniel in 8a2390a4f47
> >
> > Have the defaults for docker engine changed?
>
> No idea as I'm not following their development, but TBH it
> becomes harder and harder to use without tricks (I had to
> add systemd.unified_cgroup_hierarchy=0 to kernel cmdline
> to keep using it).
>
> Maybe I should switch to podman which is the recommended
> engine on Fedora.
>
> Cc'ing Marc-André who added podman support (Daniel is in Cc).
I'm using podman exclusively since Docker doesn't work well with
modern distros that use Cgroups v2.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-01-19 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 5:45 [RFC PATCH] tests/docker: Allow passing --network option when building images Philippe Mathieu-Daudé
2021-01-19 11:27 ` Alex Bennée
2021-01-19 13:40 ` Philippe Mathieu-Daudé
2021-01-19 14:20 ` Daniel P. Berrangé [this message]
2021-01-19 14:40 ` Philippe Mathieu-Daudé
2021-01-19 14:46 ` Daniel P. Berrangé
2021-01-19 15:58 ` Alex Bennée
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=20210119142030.GD2335568@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).