You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is quite important to fix it because there is no errors during installation and some parts of the deployment are reporting success. You need to dig into some pod logs to finally find a totally unrelated error (at least from a newcomer point of view). An error like:
error pushing image: failed to push to destination 10.103.185.129/default/camel-k-ctx-bkdlhuftt2idjd0d2ia0:3107: Head http://10.103.185.129/v2/default/camel-k-ctx-bkdlhuftt2idjd0d2ia0/blobs/sha256:b6ea704449b4b3b4fc99025edc9aea6cc5ec26660a40e57523bff8f13eb088e2: dial tcp 10.103.185.129:80: connect: connection refused
The text was updated successfully, but these errors were encountered:
this page https://camel.apache.org/staging/camel-k/latest/installation/minikube.html
is mentioning nothing about the extra parameter to provide that are mentioned on https://github.com/apache/camel-k/blob/master/docs/cluster-setup.adoc#minikube
it is quite important to fix it because there is no errors during installation and some parts of the deployment are reporting success. You need to dig into some pod logs to finally find a totally unrelated error (at least from a newcomer point of view). An error like:
error pushing image: failed to push to destination 10.103.185.129/default/camel-k-ctx-bkdlhuftt2idjd0d2ia0:3107: Head http://10.103.185.129/v2/default/camel-k-ctx-bkdlhuftt2idjd0d2ia0/blobs/sha256:b6ea704449b4b3b4fc99025edc9aea6cc5ec26660a40e57523bff8f13eb088e2: dial tcp 10.103.185.129:80: connect: connection refused
The text was updated successfully, but these errors were encountered: