From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Claudio Fontana" <cfontana@suse.de>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: check-tcg errors (build-user, build-user-plugins) again
Date: Wed, 2 Dec 2020 15:25:49 +0100 [thread overview]
Message-ID: <f7f41ce9-450d-f71d-fe69-74abd0593514@redhat.com> (raw)
In-Reply-To: <b39faaa4-3be7-2e05-226c-7a3e50ab75af@suse.de>
On 12/2/20 12:25 PM, Claudio Fontana wrote:
> On 12/2/20 12:16 PM, Alex Bennée wrote:
>> Claudio Fontana <cfontana@suse.de> writes:
>>> Is there some pre-configuration on the host necessary to be able to
>>> run check-tcg?
>>
>> There shouldn't be but those errors remind me of some of the tweaks I
>> had to make to me Gentoo system when using podman (instead of docker).
>> In the end I think I just ended up adding the lines:
>>
>> alex:100000:65536
>>
>> to /etc/subgid and /etc/subgid-
>>
>> Marc-André may have some better pointers as he added podman support to
>> the builder scripts.
Not sure if helpful, but what worked for me is remove podman
and use docker... For sure I'm not testing podman, enough to
deal with docker.
> I did that and things seem a bit better, but still a lot of errors:
>
>
> 63 ../sysdeps/x86_64/start.S: No such file or directory.
>
> Error: error creating build container: The following failures happened while trying to pull image specified by "debian:bullseye-slim" based on search registries in /etc/containers/registries.conf:
> * "localhost/debian:bullseye-slim": Error initializing source docker://localhost/debian:bullseye-slim: error pinging docker registry localhost: Get https://localhost/v2/: dial tcp [::1]:443: connect: connection refused
> * "docker.io/library/debian:bullseye-slim": Error committing the finished image: error adding layer with blob "sha256:ae63fcbbc3b289e425e4c8840ccde4314f4a060cbc0345e6871a28bdc72f6fe8": Error processing tar file(exit status 1): there might not be enough IDs available in the namespace (requested 0:42 for /etc/gshadow): lchown /etc/gshadow: invalid argument
> Traceback (most recent call last):
> File "/home/claudio/git/qemu-pristine/qemu/tests/docker/docker.py", line 709, in <module>
> sys.exit(main())
> File "/home/claudio/git/qemu-pristine/qemu/tests/docker/docker.py", line 705, in main
> return args.cmdobj.run(args, argv)
> File "/home/claudio/git/qemu-pristine/qemu/tests/docker/docker.py", line 501, in run
> extra_files_cksum=cksum)
> File "/home/claudio/git/qemu-pristine/qemu/tests/docker/docker.py", line 354, in build_image
> quiet=quiet)
> File "/home/claudio/git/qemu-pristine/qemu/tests/docker/docker.py", line 244, in _do_check
> return subprocess.check_call(self._command + cmd, **kwargs)
> File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call
> raise CalledProcessError(retcode, cmd)
>
>
> [...]
> Error: error pulling image "registry.gitlab.com/qemu-project/qemu/qemu/fedora-cris-cross": unable to pull registry.gitlab.com/qemu-project/
Maybe you need "use explicit docker.io registry" from Daniel:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg763484.html
[...]
next prev parent reply other threads:[~2020-12-02 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 9:32 check-tcg errors (build-user, build-user-plugins) again Claudio Fontana
2020-12-02 11:16 ` Alex Bennée
2020-12-02 11:25 ` Claudio Fontana
2020-12-02 12:52 ` Alex Bennée
2020-12-02 14:24 ` Claudio Fontana
2020-12-02 14:25 ` Philippe Mathieu-Daudé [this message]
2021-01-10 21:17 ` check-tcg HOWTO? Claudio Fontana
2021-01-11 13:35 ` Alex Bennée
2021-01-11 14:47 ` Claudio Fontana
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=f7f41ce9-450d-f71d-fe69-74abd0593514@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=marcandre.lureau@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).