From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab containers are broken
Date: Thu, 4 Feb 2021 10:00:09 +0000 [thread overview]
Message-ID: <20210204100009.GE549438@redhat.com> (raw)
In-Reply-To: <6ec7bebe-587d-df2d-0221-e12cb6f4c775@redhat.com>
On Thu, Feb 04, 2021 at 09:08:13AM +0100, Thomas Huth wrote:
> On 04/02/2021 07.27, Richard Henderson wrote:
> > On 2/3/21 8:03 PM, Thomas Huth wrote:
> > > On 04/02/2021 00.04, Richard Henderson wrote:
> > > > Something has gone wrong with the building of the containers
> > > > in gitlab, because *all* off them are installing Alpine Linux.
> > > >
> > > > https://gitlab.com/rth7680/qemu/-/jobs/1006336396#L155
> > >
> > > I think that's ok ... the output about alpine that you see there is just the
> > > output from the container that builds the final container. Later you can see
> > > some "yum install" lines in that output, too, that's where the CentOS container
> > > gets build. And the final compilation job runs on CentOS, too:
> > >
> > > https://gitlab.com/rth7680/qemu/-/jobs/1006336699#L35
> > >
> > > (look for the string "Red Hat" there)
> >
> > Hmm. Is there any way to get the full output of the container build? At
> > present it's being truncated:
> >
> > #7 [4/5] RUN yum install -y bzip2 bzip2-devel ccache csnappy-de...
> >
> >
> > In particular, I'm trying to add a new test, and I have added libffi-devel.i686
> > to the fedora-i386-cross.docker file, but then the actual build fails because
> > the libffi header file is missing.
> >
> > I know you may need the actual patch to comment, but pointers to how to debug
> > this sort of failure are welcome.
>
> I don't have a clue, all that container magic has been done by Daniel
> initially - maybe he can help (now on CC:) ...
I honestly never bother with the local QEMU container build sripts as
they've over-engineered IMHO. If I need to debug something locally
I'd just do "podman build -f path/to/docker-file /path/to/docker-dir".
Alternatively just make your changes to the dockerfiles and thne push
the branch to gitlab. Gitlab will run the build and you can pull down
the docker image from your fork's docker registry
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-02-04 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 23:04 gitlab containers are broken Richard Henderson
2021-02-04 6:03 ` Thomas Huth
2021-02-04 6:27 ` Richard Henderson
2021-02-04 8:08 ` Thomas Huth
2021-02-04 10:00 ` Daniel P. Berrangé [this message]
2021-02-04 17:36 ` Richard Henderson
2021-02-04 17:37 ` Daniel P. Berrangé
2021-02-04 18:27 ` Richard Henderson
2021-02-04 18:58 ` Daniel P. Berrangé
2021-02-04 19:09 ` Richard Henderson
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=20210204100009.GE549438@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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 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).