-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Revert "Dockerfile: update containerd binary to v2.0.0" #5546
Conversation
This reverts commit b1adeed. Signed-off-by: Tonis Tiigi <[email protected]>
I think we could if we have self-hosted runners on arm64 but don't think we have any atm. |
For this specific issue, I think just cross-compiling the stage would have done it. |
@tonistiigi see this PR as well in containerd packaging; it has some links as well; |
Oh right we don't release containerd bin. We could cross-comp indeed. |
Tried: diff --git a/Dockerfile b/Dockerfile
index 576c5e368..cef01dd7c 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -204,7 +204,7 @@ FROM gobuild-base AS containerd-build
WORKDIR /go/src/github.com/containerd/containerd
ARG TARGETPLATFORM
ENV CGO_ENABLED=1 BUILDTAGS=no_btrfs GO111MODULE=off
-RUN xx-apk add musl-dev gcc && xx-go --wrap
+RUN xx-apk add musl-dev gcc binutils-gold && xx-go --wrap
COPY --chmod=755 <<-EOT /build.sh
#!/bin/sh
set -ex No success 😞
|
@AkihiroSuda You wouldn't use |
This reverts commit b1adeed.
Building for arm64 fails.
--platform=linux/amd64
is ok and this is why CI is ok. We might need to make sure that integration tests stage is tested on arm64 as well (even if tests actually don't run this way).@AkihiroSuda If you can provide immediate fix then this can be closed. Otherwise revert and then reenable later.