-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add mutli arch build and manifest for the operator repo #11
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11 +/- ##
=======================================
Coverage 26.38% 26.38%
=======================================
Files 75 75
Lines 5021 5021
=======================================
Hits 1325 1325
Misses 3532 3532
Partials 164 164
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Looks good. Just cosmetic changes.
cb4c9de
to
06a36ba
Compare
Makefile
Outdated
.PHONY: manifest-build | ||
manifest-build: ## Build MULTIARCH_TARGETS manifest for bpfman-operator and bpfman-agent. | ||
echo 'building manifest for $(BPFMAN_OPERATOR_IMG) and $(BPFMAN_AGENT_IMG)' | ||
DOCKER_BUILDKIT=1 $(OCI_BIN) rmi ${BPFMAN_OPERATOR_IMG} -f |
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.
What happens here if $(OCI_BIN) is podman? the DOCKER_BUILDKIT=1
won't have any effect in that scenario right?
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.
Would it still work?
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.
OCI_BIN is docker if u have docker installed
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.
DOCKER_BUILDKIT
is indeed ignored using podman however it works fine here (tested locally)
In addition to that, since docker engine 23, buildkit is the default behavior so we could even get rid of it if we mention this as prereqs in the README
Makefile
Outdated
# build a single arch target provided as argument | ||
define build_target | ||
echo 'building $(1) for arch $(2)'; \ | ||
DOCKER_BUILDKIT=1 $(OCI_BIN) buildx build --load --build-arg TARGETPLATFORM=linux/$(2)\ |
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.
Again will this work if OCI_BIN is podman?
a438509
to
85a029e
Compare
48ad0c6
to
6d7564a
Compare
065706b
to
a3acdb0
Compare
Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com>
LGTM |
Fix catalog 4.18
MULTIARCH_TARGETS="ppc64le s390x" BPFMAN_AGENT_IMG=quay.io/bpfman/bpfman-agent:lastest BPFMAN_OPERATOR_IMG=quay.io/bpfman/bpfman-operator:latest make build-images
will result in