From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Camilla Conte <cconte@redhat.com>,
qemu-devel@nongnu.org, thuth@redhat.com,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v2 2/5] Use docker "stable" tag
Date: Tue, 30 May 2023 18:49:31 +0100 [thread overview]
Message-ID: <ZHY3K88Qs83W3ZPY@redhat.com> (raw)
In-Reply-To: <ZHY0zjnzp6/RSa7Y@redhat.com>
On Tue, May 30, 2023 at 06:39:26PM +0100, Daniel P. Berrangé wrote:
> On Mon, May 22, 2023 at 06:41:51PM +0100, Camilla Conte wrote:
> > Use the same tag in all jobs.
> >
> > Signed-off-by: Camilla Conte <cconte@redhat.com>
> > ---
> > .gitlab-ci.d/container-template.yml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/.gitlab-ci.d/container-template.yml b/.gitlab-ci.d/container-template.yml
> > index 519b8a9482..11569dd900 100644
> > --- a/.gitlab-ci.d/container-template.yml
> > +++ b/.gitlab-ci.d/container-template.yml
> > @@ -3,7 +3,7 @@
> > image: docker:stable
> > stage: containers
> > services:
> > - - docker:dind
> > + - docker:stable-dind
>
> For reasons I don't understand, this change is responsible for all our
> failed CI jobs involving Fedora being unable to resolve DNS
> AFAICT, the ':stable-dind' and ':stable' tags are no longer even supported.
And I found confirmation of this:
https://github.com/docker-library/docker/commit/606c63960a4845af7077721eb3900c706f5d0c5e
"This will remove the "test" and "stable" aliases for whatever
major release comes after 19.03 (so once the next release comes
out, "stable" will become a stale alias).
I'm not 100% sure this is the right answer, but the "stable"
alias has definitely been a huge source of confusion very
recently (and it doesn't have much meaning anymore anyways
given the death of the "edge" channel)."
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-30 17:50 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é [this message]
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é
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=ZHY3K88Qs83W3ZPY@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.