Closed bvahdat closed 6 months ago
It seems the problem is not directly on Camel K side, but in the registry that for some reason cannot parse correctly the tag due to the presence of 2 colons. Likely it's this issue that seem to affect Harbor registries: https://github.com/GoogleContainerTools/kaniko/issues/2414
Closing for now, as at this stage we cannot do much more to help with this problem.
Thanks @squakez for looking into this.
So what this means is that currently using minikube registry with it's default port 5000
one can not run any camel-k integration. Maybe this needs to mentioned here?
I am looking more carefully at this and I think the error message you got is misleading. Having another look at the operator log, it seems you're connecting to a registry expected to be found at locahost
, that means, on the same Pod where the operator is running. When specifying the registry, you need to provide a resolvable address for the Pod where the operator is running.
... it seems you're connecting to a registry expected to be found at locahost, that means, on the same Pod where the operator is running ...
Thanks @squakez. As already provided by the command snippets I make use of port-forwarding which should do the job using localhost
.
By any chance, would you be able to run the hello.groovy sample on minikube and see if that would work for you (using minikube's own registry addon and not docker registry or something else)?
I think the port forward is meant to expose a Kubernetes service in your host machine and not the other way around. If you are using a registry as a Pod [1] (which is already done ootb by Minikube) you need to provide the IP to the operator. As you're running the operator in Minikube, there is no need to provide the --registry
option during installation as it will be discovered by the tooling.
[1] https://camel.apache.org/camel-k/2.2.x/installation/registry/own.html#configuring-registry-run-pod
... there is no need to provide the --registry option during installation as it will be discovered by the tooling.
Thanks @squakez, that did the trick 👍
What happened?
It seems when the registry has a port other than the default
80
then parsing the registry URL for pushing the tag fails. For more details see also https://camel.zulipchat.com/#narrow/stream/257299-camel-k/topic/repository.20can.20only.20contain.20the.20characters.2E.2E.2EPlease note that I don't make use of the
docker
driver butqemu
, though I believe that would make no difference in the observed behaviour.Steps to reproduce
Running on a
Apple M1 ARM64
machine here the steps I ran into this problem:install minikube
verify the registry is running properly
do port forwarding
verify that port forwarding works
install kamel CLI
verify the created POD
run hello.groovy from the camel-k documentation
Relevant log output
Camel K version
2.2.0