0
1.4K
VistasDocker OCI runtime create failed: container_linux.go:349: starting container process caused
I have been working on a project for almost a year, and this project has been working in Docker. Today I noticed that the permissions of the entire file system changed to 777 (all files "-rwxrwxrwx"). I don’t know why all this happened and I wanted to fix it.
I ran two Bash command:
find ./ -type -d exec chmod 755 {} \;
find ./ -type -f exec chmod 644 {} \;
After that I wanted to see the result and I run this command ls -l and I saw such a message Permission denied, the worst thing that could happen. I could not run a single command, and decided to get out of the container. After that the nightmare began. And now when I try to start the container again I get the following error
Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown
Error: failed to start containers:
I do not want to think about the worst, because I can’t afford to lose this container, I really need it. My OS Ubuntu 18.04.
4 Respuestas
Responde la pregunta0
In my case, to resolve the error message, I also had to enable the integration between Docker Desktop for Windows and the Ubuntu distro running on WSL2. I installed the distro after Docker Desktop and forgot about this step.
0
Adding "bash" in the Entrypoint worked for me:
ENTRYPOINT ["bash","entrypoint.prod.sh"]
0
First check the service status:
systemctl status docker
Try a restart:
systemctl restart docker
I had the same issue and the solution for me it was to update the unit file /etc/systemd/system/docker.service (systemctl edit docker.service) more exactly I deleted the MountFlags=slave from the unit file and afterwards systemctl daemon-reload.
0
I had this error after a dnf update on Fedora 34 which included a Docker update.
Downgrading containerd.io worked for me.
sudo dnf downgrade containerd.io