-
Notifications
You must be signed in to change notification settings - Fork 18.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
Docker unable to run containers due to containerd and shim trying to find non existing container. #38742
Comments
I was trying this on 3 other machines now and one of them has the exact same issue. The additional one with the issue is actually my desktop while all other machines (including the one mentioned above) are servers hosted on KVM. |
Sorry for changing the title. I wasn't sure if this is Docker or Docker CE related. I am using the CE version. I've did some further testing on a working and a non working KVM machine. I've made sure both systems have the exact same versions of the Kernel and Docker. Kernel config is the same as well. I've also enabled debug mode on both Docker instances and tried running this command:
Output on the machine with working Docker:
Output of the machine with broken Docker:
Both machines running Gentoo Linux with ext4 file system on KVM and the versions as shown in the initial post and it was working fine on both machines prior of updating to latest Docker. |
Hi r7l, From which version to which did you upgrade? cheers |
I was searching for the issue for 2 days now and did quite some back and forth on my system and finally found the cause. I had an unstable version of GO installed and that was causing the issue. Once i've installed the stable version of GO the problem vanished. I was updating from 18.06.2 to 18.09.2. Running this unstable version of GO wasn't an issue with the old version but is one with the current one. I can live with the stable version of GO and for that reason i'll close this issue. Thanks allot for looking into it. |
Hello,
Docker stopped working after an update. It was working fine for weeks but now fails to run ANY image.
Description
When trying to run a container with Docker it simply responds with an error message like this:
It seems like as if containerd is trying to delete a non existing container. I've deleted everything and uninstalled Docker to reinstall it again. The error remains.
I saw others mentioning a problem with logging. Docker is logging fine to the files i've set it up to. It was doing so all the time.
Steps to reproduce the issue:
/etc/init.d/docker start
docker run -it IMAGE
Describe the results you received:
Docker just displays this error:
This is the output in log file:
Describe the results you expected:
Run the container.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: