camel-k: Integration builds fail with arm64 base image
What happened?
When Camel K is run on arm64 architecture the user needs to use a different base image for integrations (e.g. --base-image=arm64v8/eclipse-temurin:17).
When the Camel K operator builds integration kit image (strategy=routine) for Integrations the build fails in the operator with Jib not being able to use this arm64 base image.
A workaround is to use a a specific image digest on the base image (e.g. --base-image=arm64v8/eclipse-temurin:17@sha256:321ac6af97a11d5aa5a580d1635ab6f945582b00eea1fe672f0cbb437b4293c8). With this all Integration builds succeed as expected.
Steps to reproduce
- Install Camel K on arm64 arch (
kamel install --operator-image=apache/camel-k:2.3.0-SNAPSHOT-arm64 --base-image=arm64v8/eclipse-temurin:17) - Run an Integration and review build log output in operator logs - see the build failing
Relevant log output
{"level":"error","ts":"2024-03-11T08:26:16Z","logger":"camel-k.maven.build","msg":"arm64v8/eclipse-temurin:17 is a manifest list, but the list does not contain an image for architecture=amd64, os=linux. If your intention was to specify a platform for your image, see https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#how-do-i-specify-a-platform-in-the-manifest-list-or-oci-index-of-a-base-image","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.6.0/errgroup/errgroup.go:78"}
Camel K version
2.3.0-SNAPSHOT
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- fix(#5238): Integration builds fail with arm64 base image — committed to squakez/camel-k by tdiesler 3 years ago
- fix(#5238): Integration builds fail with arm64 base image — committed to apache/camel-k by tdiesler 3 years ago
- feat: set package log level with logging trait doc: generated documentation chore: added E2E test for logging category chore: changed e2e test to use IntegrationLogs doc: generated documentation ... — committed to realMartinez/camel-k by realMartinez 3 years ago
- doc: generated documentation chore: added E2E test for logging category chore: changed e2e test to use IntegrationLogs doc: generated documentation chore: nightly automatic updates fix(trait): de... — committed to realMartinez/camel-k by realMartinez 3 years ago
- fix(#5238): Fix Jib integration build - Set proper Jib config home env var to writable directory in the Docker image - Set proper Jib cache directory to writable directory in the Docker image — committed to christophd/camel-k by christophd 3 years ago
- fix(#5238): Fix Jib integration build - Set proper Jib config home env var to writable directory in the Docker image - Set proper Jib cache directory to writable directory in the Docker image — committed to apache/camel-k by christophd 3 years ago
You can assign this to me - I wanted to look at this base image issue anyway Depends on https://github.com/apache/camel-k/pull/5200