camel-k groovy, jvm, spring-boot gives error pushing image

[BuddhiWathsala]

I installed camel-k using kamel install command and operator installed and running correctly. But camel-k-groovy, camel-k-jvm and camel-k-spring-boot weren't installed and those were in Error state as below.

NAME                                     READY     STATUS      RESTARTS   AGE
camel-k-cache                            0/1       Completed   0          7m
camel-k-groovy                           0/1       Error       0          32s
camel-k-jvm                              0/1       Error       0          44s
camel-k-kotlin                           1/1       Running     0          6s
camel-k-operator-785cc5898c-8vcd7        1/1       Running     0          7m
camel-k-spring-boot                      0/1       Error       0          20s

I refer the previous issue #194 and the solution of that didn't work. The logs of the jvm, groovy and spring-boot views as below.

INFO[0000] Downloading base image fabric8/s2i-java:3.0-java8 
2019/04/05 08:55:33 No matching credentials were found, falling back on anonymous
INFO[0003] Found sha256:9ac5acb3aa8e7e179eb1fd28cda7dac22ef7deac24f00b50cee56265fa259141 in local cache 
INFO[0003] Executing 0 build triggers                   
INFO[0004] Using files from context: [/workspace/builder-324045508/package/context] 
INFO[0004] Taking snapshot of full filesystem...        
INFO[0004] Skipping paths under /kaniko, as it is a whitelisted directory 
INFO[0004] Skipping paths under /var/run, as it is a whitelisted directory 
INFO[0004] Skipping paths under /proc, as it is a whitelisted directory 
INFO[0004] Skipping paths under /dev, as it is a whitelisted directory 
INFO[0004] Skipping paths under /sys, as it is a whitelisted directory 
INFO[0004] Skipping paths under /workspace, as it is a whitelisted directory 
INFO[0004] Using files from context: [/workspace/builder-324045508/package/context] 
INFO[0004] ADD . /deployments                           
INFO[0004] Taking snapshot of files...                  
error pushing image: failed to push to destination index.docker.io/default/camel-k-jvm:104686: unsupported status code 401; body: 

I'm using minikube version: v0.33.1 in MacOS High Sierra . Kubernetes version is

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:28:14Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"linux/amd64"}

[nicolaferraro]

Hi @BuddhiWathsala, the last error message:

error pushing image: failed to push to destination index.docker.io/default/camel-k-jvm:104686: unsupported status code 401; body: 

Indicates that index.docker.io is set on the integrationplatform as target registry, instead of the internal minikube registry.

Did you follow the guidelines for installing camel k on minikube?
Especially, before doing kamel install you should enable the registry addon, then the kamel CLI should be able to auto-configure it.

If you haven't done so, you can try to uninstall, enable the registry addon and kamel install again.

Let us know!

[BuddhiWathsala]

Thanks, @nicolaferraro for the immediate response. I close the issue.