Dockerfile:Add arm64 support for building images #10618
Conversation
|
Release note label not set, please set the appropriate release note. |
| curl -SsL https://github.com/cilium/bpf-map/releases/download/v1.0/bpf-map -o bpf-map && \ | ||
| chmod +x bpf-map && \ | ||
| strip bpf-map && \ | ||
| # | ||
| # cni/loopback |
There was a problem hiding this comment.
I think @borkmann already removed this in master.
There was a problem hiding this comment.
I checked the master branch again and the bpf-map related code still exists. “removed” mean that bpf-map is no longer required to be installed in Dockerfile.runtime?
There was a problem hiding this comment.
The PR is still in progress as it was blocked by another one to be merged first: #10542
aanm
added
pending-review
release-note/misc
Jianlin-lv
force-pushed
the
pr-support-arm64
branch
from
ba1583e
to
c7bc6e0
Compare
joestringer
added
the
dont-merge/needs-rebase
Add arm64 support for cilium-runtime and cilium-builder Signed-off-by: Jianlin Lv <Jianlin.Lv@arm.com>
Jianlin-lv
force-pushed
the
pr-support-arm64
branch
from
c7bc6e0
to
f694009
Compare
tklauser
removed
the
dont-merge/needs-rebase
|
test-me-please |
|
test-with-kernel |
|
This PR is blocked until some changes are done by @borkmann upstream. |
aanm
added
the
dont-merge/waiting-for-upstream
|
@aanm @borkmann I think that the upstream Linux changes can be done in parallel, do we need to block Docker image building on that? Also I think we still need to figure out how we can build & distribute builder images (we can distribute through quay.io / dockerhub if we push platform-dependent images, but not sure at this stage how to build them). But I believe that this workflow can also be worked on independent of this PR. |
aanm
removed
the
dont-merge/waiting-for-upstream
|
test-me-please |
Add arm64 support for cilium-runtime and cilium-builder
Signed-off-by: Jianlin Lv Jianlin.Lv@arm.com
Related: #9898
This change is