Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error creating integration context with buildStrategy: pod on minikube #666

Closed
lburgazzoli opened this issue May 19, 2019 · 2 comments
Closed

Comments

@lburgazzoli
Copy link
Contributor

Installed camel-k on a brand new installation of minikube v1.0.1 with the following add-ons installed:

addon-manager: enabled
dashboard: enabled
default-storageclass: enabled
ingress: enabled
registry: enabled
storage-provisioner: enabled

When running an integration, the related context fails to be created because of:

kaniko error pushing image: failed to push to destination 10.107.0.157/default/camel-k-ctx-bjgo4urnlc9sohaqk0d0:5133: Get http://10.107.0.157/v2/: dial tcp 10.107.0.157:80: i/o timeout

Services defined in kube-system are:

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)         AGE
default-http-backend   NodePort    10.111.212.114   <none>        80:30001/TCP    48m
kube-dns               ClusterIP   10.96.0.10       <none>        53/UDP,53/TCP   51m
kubernetes-dashboard   ClusterIP   10.98.153.186    <none>        80/TCP          48m
registry               ClusterIP   10.107.0.157     <none>        80/TCP          48m

kaniko logs:

camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0000] Downloading base image fabric8/s2i-java:3.0-java8 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko 2019/05/19 16:21:37 No matching credentials were found, falling back on anonymous
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0002] Found sha256:9ac5acb3aa8e7e179eb1fd28cda7dac22ef7deac24f00b50cee56265fa259141 in local cache 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0002] Executing 0 build triggers                   
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Using files from context: [/workspace/builder-536118689/package/context] 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Taking snapshot of full filesystem...        
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /kaniko, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /var/run, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /dev, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /proc, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /sys, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Skipping paths under /workspace, as it is a whitelisted directory 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Using files from context: [/workspace/builder-536118689/package/context] 
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] ADD . /deployments                           
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko INFO[0003] Taking snapshot of files...                  
camel-k-ctx-bjgo4urnlc9sohaqk0d0 kaniko error pushing image: failed to push to destination 10.107.0.157/default/camel-k-ctx-bjgo4urnlc9sohaqk0d0:5133: Get http://10.107.0.157/v2/: dial tcp 10.107.0.157:80: i/o timeout
@astefanutti
Copy link
Member

It may be due to an issue with the registry add-on that has been solved by @zregvart in kubernetes/minikube#4220.

@lburgazzoli
Copy link
Contributor Author

@zregvart @astefanutti yes that was the issue, thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants