-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
skaffold dev fails to push image to minikube with non-default profile #1205
Comments
Hi @gintautassulskus Is this something you still experience with Skaffold v0.20.0? |
Hi @dgageot, the issue persists with Skaffold v0.20.0. As a matter of fact, |
Hi @gintautassulskus , with the current master you can configure See #1355 |
Hi @corneliusweig, at the moment I am unable to test the use case as we are reworking our deployment system. |
@gintautassulskus can you give this another try? If the issue is solved, you could close this. |
@corneliusweig, the issue persists. It seems that |
@gintautassulskus Have you made sure, that you are using the docker daemon from minikube and set the context as local? Iow
If this is still not working, can you please provide further information from the following commands:
|
The following sequence of commands:
Yields the following infinitely repeating pair of messages
Does it work on your machine when you execute the given set of commands, @corneliusweig? |
@gintautassulskus I can't reproduce your error. The steps I took:
More information:
Be sure to run all these setup commands in the same shell. If this does not work for you, please provide similar information about your environment as above. |
@corneliusweig, finally, it worked. I had to use The only diff from yours:
|
@gintautassulskus Maybe you want to chime in on #1957 |
Expected behavior
skaffold dev
fails to deploy docker artifacts to minikube with a non-default profile.skaffold deploy
seems to be working as expected.Information
getting-started
exampleSteps to reproduce the behavior
FAILING:
eval $(minikube docker-env --profile custom)
did not help.The text was updated successfully, but these errors were encountered: