lsergio commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1842677157
Thanks. I'll have a look at the other publish strategies.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
squakez closed issue #4955: java.lang.ClassNotFoundException:
io.quarkus.bootstrap.runner.QuarkusEntryPoint
URL: https://github.com/apache/camel-k/issues/4955
--
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
squakez commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1841138876
I think the problem is the fact that Kaniko (and Buildah) needs root
privileges in order to work. When it creates the container, since it is with
root privileges, then, the artifact
lsergio commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1838506295
I'm doing `kubectl apply -f test.yaml `where `test.yaml` is:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: test
spec:
sources:
-
claudio4j commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1838489592
> Create an Integration. In my case I used one like this:
Are you creating the Integration CR yourself or using `kamel run
` ?
--
This is an automated message from the
lsergio commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1838405062
I'm running on Kubernetss 1.25 on EKS: v1.25.15-eks-4f4795d, more precisely
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
squakez commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1838092436
What Kubernetes version/distribution are you using?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
lsergio commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1836607564
@squakez I checked the container and the artifacts are there. However, to be
able to be see them, I had to edit the generated deployment and change the
securityContext from:
squakez commented on issue #4955:
URL: https://github.com/apache/camel-k/issues/4955#issuecomment-1836286658
It seems to be a problem with the container, like the application was not
really pushed. Can you verify if the generated container has the required
artifacts? Please check the image
lsergio opened a new issue, #4955:
URL: https://github.com/apache/camel-k/issues/4955
### What happened?
I'm trying to run a basic integration with Camel K 2.1 and it fails to start.
### Steps to reproduce
1. Setup a gcr repository as described in
10 matches
Mail list logo
