-
Notifications
You must be signed in to change notification settings - Fork 7
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
fix: docker
driver does not work when nodes>=2
#138
Comments
driver=docker
does not work when nodes>=2driver=docker
does not work when nodes>=2
driver=docker
does not work when nodes>=2
docker
driver does not work when nodes>=2
Hmm, I wonder if this is due defaulting the container runtime (to docker) when it previously was set to blank. I'll dig into this soon and see if I can get to the bottom of it! |
This.. is odd. I think i've found a bug with upstream. I see a similar error when I run minikube start --driver=docker --nodes=3 -p "laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaarge" -v=8 --alsologtostderr it seems sensitive to the cluster name for some reason 😕 I can't seem to reproduce it when I provide it a smaller name i.e. resource "minikube_cluster" "small" {
cluster_name = "small"
driver = "docker"
nodes = 3
cni = "auto"
} I'm also able to run this snippet fine resource "minikube_cluster" "default" {
cluster_name = "dev-local-docker"
driver = "docker"
nodes = 3
} |
Interesting; I'm going to do a cleaner test of this because I was checking |
This is a continuation of #131 for fixing
docker
driver multi-node usage. See logs below.There is still an issue with the
docker
driver inv0.3.9
; both of the following configurations need to work for this issue to be solved:Configuration using
cni=auto
:Configuration without
cni=auto
(logged below):Logs:
The text was updated successfully, but these errors were encountered: