-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1 #8227
Comments
when i try to remove gcr.io/k8s-minikube/kicbase:v0.0.10 image then to start minikube start --driver=docker
stderr:
stderr:
stderr:
stderr: X error provisioning host: Failed to start host: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=8000mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 : exit status 125 stderr:
docker inspect minikube docker pull docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10 |
@spiderGX do you mind sharing "docker info" and also the output of "docker logs minikube" |
minikube start --driver=docker --alsologtostderr
|
Can you please also share docker info? |
I don't think we have any regression tests on CentOS 7 and Docker 1.13 (a.k.a. 17.03) It's a lot older than our other platforms, so it might some have special needs... #3552 |
This error is the same that we have seen in all the other reports:
I think it is trying to inspect the volume, as if it was a container ? As in #8192 |
to pull down and changed the tag.
This is all the dependencies of Minikube
Hope this way will work for you (^^). |
I wanted to +1 this issue as I had the same problem today on a fresh minikube install. Docker info below - it's pretty current so I don't think it's necessarily a version-specific problem. The above solution did work however
|
the same error log got:
stderr:
stderr: |
minikube v1.10.1 on Centos 7.5.1804 is not supported ? |
This last error looks like the same as in #8325, some issue when updating the old config... |
The docker driver is untested on that platform, but there is no reason why it shouldn't work |
Regrettably, there isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.
we fixed the image registry issue on v1.11.0 , closing this, please if this issue. is still happenning feel free to reopend. |
still got this problem on v1.11.0 |
minikube version: v1.11.0 ubuntu 20.04 5.4.0-37-generic Docker version 19.03.11, build 42e35e61f3 |
error log:
E0521 10:30:47.920217 2700 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:
stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
! StartHost failed, but will try again: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=8000mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 : exit status 125
stdout:
stderr:
/usr/bin/docker-current: Error parsing reference: "" is not a valid repository/tag: repository name must have at least one component.
See '/usr/bin/docker-current run --help'.
E0521 10:31:17.576404 2700 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:
stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
stdout:
stderr:
/usr/bin/docker-current: Error parsing reference: "" is not a valid repository/tag: repository name must have at least one component.
See '/usr/bin/docker-current run --help'.
X error provisioning host: Failed to start host: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=8000mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 : exit status 125
stdout:
stderr:
/usr/bin/docker-current: Error parsing reference: "" is not a valid repository/tag: repository name must have at least one component.
See '/usr/bin/docker-current run --help'.
[
{
"Driver": "local",
"Labels": {
"created_by.minikube.sigs.k8s.io": "true",
"name.minikube.sigs.k8s.io": "minikube"
},
"Mountpoint": "/var/lib/docker/volumes/minikube/_data",
"Name": "minikube",
"Options": {},
"Scope": "local"
}
]
2.docker images
gcr.io/k8s-minikube/kicbase v0.0.10 e6bc41c39dc4 3 weeks ago 974 MB
The text was updated successfully, but these errors were encountered: