-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.9: docs: Fix cilium-runtime image bump instructions #18491
Conversation
This is a process that reliably works, unlike the previous one which relies on Quay.io's ability to pull images from DockerHub. It does require a core maintainer to prepare the changes, but that's fine for now since v1.9 should change infrequently now. Signed-off-by: Joe Stringer <joe@cilium.io>
932921e
to
cee633a
Compare
|
||
8. After selecting your branch click on "Start Build". | ||
$ skopeo login docker.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it ask prompt for a username?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, though I don't know what kind of configuration I may have prepared locally to make this work. I'd imagine that if someone other than Andre / I need to follow these instructions, then hopefully this step will at least ensure that they figure out how to set up skopeo correctly.
That said, this is only applicable for v1.9 as the newer branches have better infrastructure in the tree for handling these updates so we don't need to rely on developers having direct access to the upstream container repositories.
cc @tklauser FYI this will only be for the v1.9 branch. |
Only doc changes no need to re-run the CI. |
This is a process that reliably works, unlike the previous one which
relies on Quay.io's ability to pull images from DockerHub. It does
require a core maintainer to prepare the changes, but that's fine for
now since v1.9 should change infrequently now.