-
Notifications
You must be signed in to change notification settings - Fork 9.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
Fixes: #15266 All docker images of Architecture show amd64 #15270
Conversation
5bf9517
to
b3a6f98
Compare
scripts/release.sh
Outdated
@@ -261,8 +261,15 @@ main() { | |||
for TARGET_ARCH in "amd64" "arm64" "ppc64le" "s390x"; do | |||
log_callout "Pushing container images to quay.io ${RELEASE_VERSION}-${TARGET_ARCH}" | |||
maybe_run docker push "quay.io/coreos/etcd:${RELEASE_VERSION}-${TARGET_ARCH}" | |||
maybe_run docker manifest create "quay.io/coreos/etcd:${RELEASE_VERSION}-${TARGET_ARCH}" "quay.io/coreos/etcd:${RELEASE_VERSION}-${TARGET_ARCH}" |
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.
Please integrate it with existing block for creating manifest list on line 275.
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.
Please integrate it with existing block for creating manifest list on line 275.
Done, PTAL
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.
@serathius Why do you think the new place is better ?
I actually liked the previous version more:
The loop in 261 is responsible for preparing the arch-specific images and pushing them.
The loop in 275 is preparing a single multi-arch image.
After the modification the code got mixed and in my opinion is more confusing.
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.
42dfb39
to
329a61c
Compare
@serathius @ptabor can you please comment on how did this work alright earlier? thanks output for 3.5.6 |
Is there anyone here who can take a look? 😘 |
The multi-arch manifest looks good.
|
Please add a test case. You can follow #15505 |
Instead fixing all images, should we stop publishing tags other than multi-arch? There is no benefits to publishing single-arch image tags, and k8s doesn't do that. |
Done |
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.
Changes look good to me, thanks @zhangguanzhang .
Agree that it might simplify things to just publish the multi arch images in future. I've created #15594 to discuss that further.
Please resolve the workflow failures before I take a look. |
Using buildkit seems to be a simple solution to this problem 🤦♂️, @ahrtr @serathius PATL |
836ec16
to
426be57
Compare
Signed-off-by: zhangguanzhang <zhangguanzhang@qq.com>
The root cause turned out to be that builtkit wasn't enabled. Thanks @zhangguanzhang |
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.
LGTM
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.
Ah, good old docker quirks.
This solution looks much better. Thanks for diving in and finding the root issue!
@zhangguanzhang could you please backport this PR to 3.5 and 3.4? thx |
There is no test_image.sh in 3.5,so don't cherry-pick just commit? |
Yes, we need to backport #15505 firstly. Could you or @pchan finish it? It's a priority to me, so as to unblock releasing 3.5.8. |
Thanks @pchan |
@zhangguanzhang The test_image.sh file was just added into release-3.5, please go ahead to backport this PR to 3.5, thx. |
Fixes: #15266
Signed-off-by: zhangguanzhang zhangguanzhang@qq.com
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.