From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab docker registries
Date: Mon, 26 Jan 2026 23:44:51 +0000 [thread overview]
Message-ID: <87jyx4c51o.fsf@draig.linaro.org> (raw)
In-Reply-To: <c12f3294-1ef1-41fe-a453-1422063b991d@linaro.org> (Pierrick Bouvier's message of "Mon, 26 Jan 2026 14:12:56 -0800")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> On 1/26/26 2:05 PM, Stefan Hajnoczi wrote:
>> On Mon, Jan 26, 2026 at 4:55 PM Richard Henderson
>> <richard.henderson@linaro.org> wrote:
>>>
>>> Hiya,
>>>
>>> I noticed this today, wondering why the daily scheduled builds are failing:
>>>
>>> https://gitlab.com/qemu-project/qemu/-/jobs/12868286187
>>>
>>> time="2026-01-26T17:34:06Z" level=fatal msg="Error parsing image name
>>> \"docker://registry.gitlab.com/qemu-project/qemu/qemu/emsdk-wasm-cross\": reading manifest
>>> latest in registry.gitlab.com/qemu-project/qemu/qemu/emsdk-wasm-cross: manifest unknown"
>>> make: *** [tests/docker/Makefile.include:54: docker-verify-emsdk-wasm-cross] Error 2
>>>
>>> I'm not really sure what the error message means. Do we need to push a built version of
>>> emsdk-wasm-cross to gitlab, so that a manifest is present? Which doesn't make much sense,
>>> since the job is all about a weekly rebuild of the containers.
>>
>> I don't see that container image in the registry:
>> https://gitlab.com/qemu-project/qemu/container_registry?orderBy=UPDATED&sort=desc&search[]=wasm
>> Only the emsdk-wasm32-cross and emsdk-wasm64-cross images are there.
>> Stefan
>>
>
> I don't see where the job that is supposed to build containers weekly
> is building them, it is just calling skopeo inspect (???).
>
> It should depend on building and pushing associated image.
>
it depends on:
- wasm64-emsdk-cross-container
is that build failing?
> https://gitlab.com/qemu-project/qemu/-/commit/8bec7b9874235e60f14172618121c60fdbd39302
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-01-26 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 21:53 gitlab docker registries Richard Henderson
2026-01-26 22:05 ` Stefan Hajnoczi
2026-01-26 22:12 ` Pierrick Bouvier
2026-01-26 23:44 ` Alex Bennée [this message]
2026-01-27 2:15 ` Richard Henderson
2026-01-26 23:50 ` Alex Bennée
2026-01-27 2:15 ` Richard Henderson
2026-01-27 9:28 ` Alex Bennée
2026-01-27 17:10 ` Pierrick Bouvier
2026-01-27 17:31 ` Pierrick Bouvier
2026-01-27 18:15 ` Alex Bennée
2026-01-27 18:28 ` Pierrick Bouvier
2026-01-27 23:51 ` Alex Bennée
2026-01-28 17:08 ` Pierrick Bouvier
2026-01-26 22:07 ` Pierrick Bouvier
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=87jyx4c51o.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@gmail.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.