Error pushing image to camel-k-ctx

[bruno63]

Have installed Camel-K on minikube like this:

minikube start —vm-driver hyperkit
minikube addons enable registry
kamel install --cluster-setup
kamel install

everything ok so far, no errors.

Starting the simple example ( kamel run helloworld.groovy ) fails with

error pushing image: failed to push to destination 10.107.193.242/default/camel-k-ctx-bkrdq13bk2vlabjbj540:881: Head http://10.107.193.242/v2/default/camel-k-ctx-bkrdq13bk2vlabjbj540/blobs/sha256:05edc034e41df2d2ad717d7c25fc8cb67a6d4ff3cce444fdf5d52138d5ebd7d2: dial tcp 10.107.193.242:80: connect: connection refused

It is the same error message as in Issue-798. Trying to start minikube with the extra-config did not help either:

minikube start --extra-config=apiserver.enable-admission-plugins="LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,MutatingAdmissionWebhook" —vm-driver hyperkit

The error remained the same.
Same behaviour also when trying to run other examples.

Versions:
OS: macOS Catalina 10.15 beta
Minikube: 1.2.0
Camel K Client: 0.3.4

Full log of camel-k-ctx pod (from kaniko):
INFO[0000] Downloading base image fabric8/s2i-java:3.0-java8
2019/07/23 10:13:43 No matching credentials were found, falling back on anonymous
INFO[0002] Found sha256:9ac5acb3aa8e7e179eb1fd28cda7dac22ef7deac24f00b50cee56265fa259141 in local cache
INFO[0002] Executing 0 build triggers
INFO[0002] Using files from context: [/workspace/builder-047742163/package/context]
INFO[0002] Taking snapshot of full filesystem...
INFO[0002] Skipping paths under /kaniko, as it is a whitelisted directory
INFO[0002] Skipping paths under /var/run, as it is a whitelisted directory
INFO[0002] Skipping paths under /dev, as it is a whitelisted directory
INFO[0002] Skipping paths under /sys, as it is a whitelisted directory
INFO[0002] Skipping paths under /proc, as it is a whitelisted directory
INFO[0002] Skipping paths under /workspace, as it is a whitelisted directory
INFO[0002] Using files from context: [/workspace/builder-047742163/package/context]
INFO[0002] ADD . /deployments
INFO[0002] Taking snapshot of files...
2019/07/23 10:13:46 existing blob: sha256:b5b577af0b7eb8497b810175332e046ccf625c9f2100c323caf54865035b3da2
2019/07/23 10:13:46 existing blob: sha256:7ce2999189a0ad5b82e4780a5f6300aa1db7f7a7df0ce0a2f7fd40c3e9ef4e80
2019/07/23 10:13:46 existing blob: sha256:8d8128fbd7d1931e3c8afd8968f28136afb8df54eb0505ad51a01508354a86ed
2019/07/23 10:13:46 existing blob: sha256:973c34d54acc024c9e64f837fc0cd0eb459a093a4c63e0f6709eb788012b5a14
2019/07/23 10:13:46 existing blob: sha256:485b81c55d61f54bf60dcbb2f1d1a9e710df1f30fa8917187f5a1b6f64e7d77c
2019/07/23 10:13:46 existing blob: sha256:a02a4930cb5d36f3290eb84f4bfa30668ef2e9fe3a1fb73ec015fc58b9958b17
2019/07/23 10:13:46 existing blob: sha256:39eeeac7df7d16ed9869c55dfcb5ce6de7f96c2fdc6d0b917d77488f0cf129f7
2019/07/23 10:13:46 pushed blob sha256:0c38442293fea27fd609dfbb61b05bd2b1772d60bfda82555b98208b155a6b04
2019/07/23 10:13:46 pushed blob sha256:2896531f72e07876c0d62eb347d95c5244abc7929b60fba60e57e11dc9f15ba3
2019/07/23 10:13:46 pushed blob sha256:da9d18637ef180b49a56c5a9fcf9f3d3ebc3474da1aec41bc57e5b3184bfbcb5
2019/07/23 10:13:46 pushed blob sha256:0301dc50ab0aaf83ab16e50023eba35b0b6f312d48c7fb00b409005d8e6ec638
2019/07/23 10:13:46 pushed blob sha256:f0d42cde87edbd2ec6e7c1aa1be71d2ac77c383aa15aea4f6656ee958d116f81
2019/07/23 10:13:46 pushed blob sha256:b6ea704449b4b3b4fc99025edc9aea6cc5ec26660a40e57523bff8f13eb088e2
2019/07/23 10:13:46 pushed blob sha256:573b0cfdcdbd615602dd292efd6c07d813e703c7adc8f354dcde6c7ac4312116
error pushing image: failed to push to destination 10.107.193.242/default/camel-k-ctx-bkrdq13bk2vlabjbj540:881: Head http://10.107.193.242/v2/default/camel-k-ctx-bkrdq13bk2vlabjbj540/blobs/sha256:05edc034e41df2d2ad717d7c25fc8cb67a6d4ff3cce444fdf5d52138d5ebd7d2: dial tcp 10.107.193.242:80: connect: connection refused

[lburgazzoli]

There is an issue with the registry addon in minikube, see this commit for a fix: kubernetes/minikube@d76d874#diff-2e9f0db5aa2b1e883b263b7ebc11d869

[bruno63]

Thanks for the quick response. Will try to apply the fix.

[lburgazzoli]

let me know if it works or if you hit a different bug

[bruno63]

Update: this issue seems to be solved with latest versions Minikube v1.6.2, kubectl 1.17.2, Camel K Client 1.0.0-RC1.

[github-actions]

This issue is stale because it has been open 30 days with no activity.
Remove stale label or comment or this will be closed in 7 days.