Docker OCI运行时创建失败:container_linux.go:349:导致启动容器进程 [英] Docker OCI runtime create failed: container_linux.go:349: starting container process caused

问题描述

我已经在一个项目上工作了将近一年，并且这个项目已经在Docker中工作了.今天，我注意到整个文件系统的权限更改为777(所有文件均为"-rwxrwxrwx").我不知道为什么会发生所有这些事情，所以我想修复它.

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.

我运行了两个Bash命令:

I ran two Bash command:

find ./ -type -d exec chmod 755 {} \;
find ./ -type -f exec chmod 644 {} \;

此后，我想查看结果，然后运行此命令 ls -l <​​/code>，我看到了这样的消息:权限被拒绝，这可能是最糟糕的事情.我无法运行单个命令，因此决定退出该容器.之后，噩梦开始了.现在，当我尝试再次启动容器时，出现以下错误

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:

我不想考虑最坏的情况，因为我承受不起丢掉这个容器的麻烦，我真的很需要它.我的操作系统Ubuntu 18.04.

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.

推荐答案

在入口点添加"bash"对我有用:

Adding "bash" in the Entrypoint worked for me:

ENTRYPOINT ["bash","entrypoint.prod.sh"]

这篇关于Docker OCI运行时创建失败:container_linux.go:349:导致启动容器进程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！