You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "christophd (via GitHub)" <gi...@apache.org> on 2024/03/11 08:43:12 UTC
[I] Integration builds fail with arm64 base image [camel-k]
christophd opened a new issue, #5238:
URL: https://github.com/apache/camel-k/issues/5238
### 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
1. Install Camel K on arm64 arch (`kamel install --operator-image=apache/camel-k:2.3.0-SNAPSHOT-arm64 --base-image=arm64v8/eclipse-temurin:17`)
2. Run an Integration and review build log output in operator logs - see the build failing
### Relevant log output
```shell
{"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\ngo
lang.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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022338680
> docker.io/apache/camel-k:2.3.0-SNAPSHOT-arm64 is no longer valid
why is `make images` building this image then?
> Also, mind that when you make images you should not run --operator-image docker.io/apache..., otherwise you'd be using the image published in docker instead of your local own.
I have switched to Podman recently and this is how the image gets pushed to the Minikube registry using the `docker.io/` prefix. I need to use the prefix but I guess this is MacOS specific when using the Minikube VM
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1993732599
PR: https://github.com/apache/camel-k/pull/5246
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022228172
`docker.io/apache/camel-k:2.3.0-SNAPSHOT-arm64` is no longer valid. I think you need to install normal `docker.io/apache/camel-k:2.3.0-SNAPSHOT`. The cluster will pick the correct platform from the manifest. We amended the previous documentation https://camel.apache.org/camel-k/next/installation/advanced/multi-architecture.html
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1991655127
That only happens in ARM I think. For some reason it looks by default for amd64 image and can't find it, but when you give the digest it pull the image you configured. I wonder if we have the same issue with spectrum.
Maybe this https://github.com/apache/camel-k/pull/5200 will fix this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2003459798
> I guess that means by default we will create images compatible with both platforms.
No sure that this is actually true. For now I assume that the integration image (singular) is built to run on the platform that invokes the build. Whether and how the build output is also portable to other archs would be another issue, with lots of testing and documentation to be done
In short, this PR is a fix to the issue at hand - no (positive) side effects implied
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1993650446
You can assign this to me - I wanted to look at this base image issue anyway
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022182481
Sorry, I have to reopen this issue as all integration builds fail on host with `arm64` architecture.
This is the error I get in the Camel K operator with `2.3.0-SNAPSHOT` built from main branch:
```
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.4.1:build (default-cli) on project camel-k-integration: Failed to create, open, or parse global Jib config file; see https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#where-is-the-global-jib-configuration-file-and-how-i-can-configure-it to fix or you may need to delete /.config/google-cloud-tools-java/jib/config.json -> [Help 1]","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"}
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"","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"}
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"To see the full stack trace of the errors, re-run Maven with the -e switch.","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"}
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"Re-run Maven using the -X switch to enable full debug logging.","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"}
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"","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"}
{"level":"error","ts":"2024-03-27T08:11:04Z","logger":"camel-k.maven.build","msg":"For more information about the errors and possible solutions, please read the following articles:","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"}
```
I am running on Minikube on a Mac M1 arm64.
What I did to build the Camel K image is `make images` and install the operator with:
```
kamel install --global --operator-image docker.io/apache/camel-k:2.3.0-SNAPSHOT-arm64 --base-image eclipse-temurin:17@sha256:321ac6af97a11d5aa5a580d1635ab6f945582b00eea1fe672f0cbb437b4293c8
```
I also tried to use the base image `arm64v8/eclipse-temurin:17` with same result
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1996879169
During build time, we extract the base image digest from the manifest list, like this ...
```
ARM64_DIGEST := $(shell docker manifest inspect eclipse-temurin:17 | jq -r '.manifests[] | select(.platform.architecture == "arm64") | .digest')
```
We use that base image, if no other was explicitly defined
```
$ kamel install --olm=false --operator-image apache/camel-k:2.3.0-SNAPSHOT
Using linux/arm64 base image: eclipse-temurin:17@sha256:321ac6af97a11d5aa5a580d1635ab6f945582b00eea1fe672f0cbb437b4293c8
Camel K installed in namespace default
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022341442
`docker.io/apache/camel-k:2.3.0-SNAPSHOT-arm64` image works good for me. This is not the issue. the issue is that the integration base image for `arm64` architecture is not working with jib build in the operator
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1997537212
In this second attempt, we simply tell Jib to consider multiple platforms for the FROM image
```
-Djib.from.platforms=linux/amd64,linux/arm64 -Djib.from.image=eclipse-temurin:17
```
I also upgraded to jib-3.4.1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1997598404
@christophd could you perhaps verify whether this branch works for you?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022344605
Okey, I though you were using the old nightly. In general, given we're publishing the manifest now, I think the usage of suffix is no longer required as the decision is going to be delegated to the cluster.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #5238: Integration builds fail with arm64 base image
URL: https://github.com/apache/camel-k/issues/5238
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1987976745
Thanks for pointing to the docs - I was not aware of this.
But having to use the sha256 digest prevents us from getting the very latest updates from an image stream `arm64v8/eclipse-temurin:17`, right? When there is a new update pushed to `arm64v8/eclipse-temurin:17` we need to manually adjust the base image digest on the base image.
Do we know why we need to use the digest in the base image here? Maybe @gansheer?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1993652156
Depends on #5200
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "tdiesler (via GitHub)" <gi...@apache.org>.
tdiesler commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1996900355
Slack: https://redhat-internal.slack.com/archives/C06DH6BJA80/p1710406352615669
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1997553059
> In this second attempt, we simply tell Jib to consider multiple platforms for the FROM image
>
> ```
> -Djib.from.platforms=linux/amd64,linux/arm64 -Djib.from.image=eclipse-temurin:17
> ```
>
> I also upgraded to jib-3.4.1
That's nice !
I guess that means by default we will create images compatible with both platforms.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-1987958807
This is already documented: https://camel.apache.org/camel-k/2.2.x/installation/advanced/multi-architecture.html
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022405137
In the error I can see `Failed to create, open, or parse global Jib config file` as it expects a file in `~/.config/google-cloud-tools-java/jib/config.json`. Jib will create that file if not present but I think the process lacks write permissions for that path.
We could add `XDG_CONFIG_HOME` env var and point this to a writable directory within the Docker image.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer closed issue #5238: Integration builds fail with arm64 base image
URL: https://github.com/apache/camel-k/issues/5238
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Integration builds fail with arm64 base image [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5238:
URL: https://github.com/apache/camel-k/issues/5238#issuecomment-2022231655
Also, mind that when you `make images` you should not run `--operator-image docker.io/apache...`, otherwise you'd be using the image published in docker instead of your local own.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org