From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Camilla Conte <cconte@redhat.com>,
qemu-devel@nongnu.org, thuth@redhat.com
Subject: Re: Add CI configuration for Kubernetes
Date: Tue, 23 May 2023 08:55:19 +0100 [thread overview]
Message-ID: <ZGxxZ6M7FRse47ox@redhat.com> (raw)
In-Reply-To: <d08d55dd-f38b-063c-d64e-9a0f79dbebf9@linaro.org>
On Mon, May 22, 2023 at 03:52:30PM -0700, Richard Henderson wrote:
> On 5/22/23 10:41, Camilla Conte wrote:
> > Here's a second version (v2) of patches to support the Kubernetes runner for Gitlab CI.
> > You can find the v1 thread here: https://lore.kernel.org/qemu-devel/20230407145252.32955-1-cconte@redhat.com/.
>
>
> This does not work:
>
> https://gitlab.com/qemu-project/qemu/-/pipelines/875254290
>
> In particular, most jobs spent 30 minutes (until I cancelled them), e.g.
>
> https://gitlab.com/qemu-project/qemu/-/jobs/4329346855#L7561
>
> Client:
> Debug Mode: false
> Server:
> ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
> Is the docker daemon running?
Seems the problem is with the launcher for the k8s runner which throws
a mass of warnings & errors earlier in the logs about pods not being
ready
https://gitlab.com/qemu-project/qemu/-/jobs/4329346855#L12
With 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:[~2023-05-23 7:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 17:41 Add CI configuration for Kubernetes Camilla Conte
2023-05-22 17:41 ` [PATCH v2 1/5] Remove redundant CI variables Camilla Conte
2023-05-23 8:32 ` Daniel P. Berrangé
2023-05-22 17:41 ` [PATCH v2 2/5] Use docker "stable" tag Camilla Conte
2023-05-23 8:33 ` Daniel P. Berrangé
2023-05-30 17:39 ` Daniel P. Berrangé
2023-05-30 17:49 ` Daniel P. Berrangé
2023-05-30 17:53 ` Richard Henderson
2023-05-22 17:41 ` [PATCH v2 3/5] Add loop over docker info Camilla Conte
2023-05-23 8:33 ` Daniel P. Berrangé
2023-05-23 13:06 ` Richard Henderson
2023-05-23 13:26 ` Camilla Conte
2023-05-22 17:41 ` [PATCH v2 4/5] Add CI variable RUNNER_TAG Camilla Conte
2023-05-23 8:34 ` Daniel P. Berrangé
2023-05-22 17:41 ` [PATCH v2 5/5] Add Kubernetes runner configuration Camilla Conte
2023-05-23 8:37 ` Daniel P. Berrangé
2023-05-22 22:52 ` Add CI configuration for Kubernetes Richard Henderson
2023-05-23 7:55 ` Daniel P. Berrangé [this message]
2023-05-23 8:24 ` Camilla Conte
2023-05-23 13:07 ` Richard Henderson
2023-05-23 13:28 ` Camilla Conte
2023-05-23 12:49 ` [PATCH v3 5/5] Add Kubernetes runner configuration Camilla Conte
2023-05-24 21:23 ` Add CI configuration for Kubernetes 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=ZGxxZ6M7FRse47ox@redhat.com \
--to=berrange@redhat.com \
--cc=cconte@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 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.