From: Eldon Stegall <eldon-qemu@eldondev.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: New container build error: mountpoint does not exit
Date: Thu, 25 May 2023 04:12:27 +0000 [thread overview]
Message-ID: <ZG7gK6ZFgSSvBGBV@invalid> (raw)
In-Reply-To: <b7ef4d65-1b2c-c435-b448-9b6bec39cd96@linaro.org>
On Wed, May 24, 2023 at 01:09:30PM -0700, Richard Henderson wrote:
> Hi Eldon,
>
> New this morning are some odd failures in the container build stage, e.g
>
> https://gitlab.com/qemu-project/qemu/-/jobs/4345796216#L235
>
> cgroups: cgroup mountpoint does not exist: unknown
>
> There are several such failures in that pipeline. I've not seen this before, nor was it
> happening yesterday.
>
> Any ideas?
Hi Richard,
If I had to guess, it's probably related to some changes in
Camille's patchset. My first guess is that it is related to
https://gitlab.com/qemu-project/qemu/-/commit/5f63a67adb58478974b91f5e5c2b1222b5c7f2cc
which downgrades docker-in-docker from latest to stable-dind.
I'm not sure how the stable tags are treated with docker, but it
does seem that those tags haven't been updated in a couple of years.
This person on SO seems to have fixed a similar issue in gitlab ci
by upgrading: https://stackoverflow.com/q/70707572
The cgroups error leads me to believe that the older dind service is
expecting cgroups v1, while the hardware runner is running FCOS with
cgroups v2.
I ran a test with just that patch omitted on my repo, with better
results:
https://gitlab.com/eldondev/qemu/-/pipelines/878387857
I will see if the opensbi build which also uses stable-dind and failed
in that pipeline is successful when attempting to use latest dind
instead.
If using stable is compelling, I can work on making the hardware runner
support it.
Thanks,
Eldon
prev parent reply other threads:[~2023-05-25 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 20:09 New container build error: mountpoint does not exit Richard Henderson
2023-05-25 4:12 ` Eldon Stegall [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=ZG7gK6ZFgSSvBGBV@invalid \
--to=eldon-qemu@eldondev.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).