gansheer commented on issue #5207:
URL: https://github.com/apache/camel-k/issues/5207#issuecomment-1976832191
As far as execution goes it works as it should.
By adding the `container.image` trait you are creating a external
integration kit. As such the `jvm` trait is disabled.
Also, the `jvm` trait is disabled by default for native build case.
A workaround to have the run work as you expect is to run your image as a
source less integration and add the following pod template :
```yaml
containers:
- name: integration
command:
- ./camel-k-integration-2.3.0-SNAPSHOT-runner
workingDir: /deployments
```
Using the kamel CLI it would be : `kamel run --image=xxxxx --name external
--pod-template patch_pod.yaml`
We are back in the issue discussed
[here](https://github.com/apache/camel-k/issues/5112#issuecomment-1930342054)
about the necessity to create have the integration kit as well as the container
image in the case we want to reuse one created by the operator. As for now most
of the command configuration is described the integrationkit : the artifacts,
the type of layout (that will define if it is native or not), etc.
--
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-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
