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

docker-env stops working after IP change #8185

Closed
medyagh opened this issue May 17, 2020 · 1 comment · Fixed by #8239
Closed

docker-env stops working after IP change #8185

medyagh opened this issue May 17, 2020 · 1 comment · Fixed by #8239
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@medyagh
Copy link
Member

medyagh commented May 17, 2020

this is on docker-driver but it could be true on podman and kvm as well.

med@xmac:~/workspace/minikube (windows_gh_action)$ eval $(minikube docker-env); docker images
error during connect: Get https://172.17.0.2:2376/v1.40/images/json: x509: certificate is valid for 172.17.0.3, 127.0.0.1, not 172.17.0.2

replicate

#!/bin/bash
for i in {1..5}
do
   echo "try $i"
   minikube start -p minikube
   minikube start -p p1
   minikube start -p p2
   eval $(minikube docker-env -p minikube)
   docker images
   eval $(minikube docker-env -p p1)
   docker images
   eval $(minikube docker-env -p p2)
   docker images
   minikube stop -p minikube & minikube stop -p p1 & minikube stop -p p2
   systemctl restart docker
done

solution

restaring the docker inside minikube makes docker to pick the certs.

@medyagh medyagh added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 17, 2020
@medyagh medyagh added this to the v1.11.0 May28 milestone May 17, 2020
@afbjorklund
Copy link
Collaborator

I think this got broken in 1.9.0, need to verify that with 1.8.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants