简体   繁体   English

exec:“docker-runc”:在$ PATH中找不到可执行文件:未知

[英]exec: “docker-runc”: executable file not found in $PATH: unknown

Using ubuntu 18.04 after upgrading docker to "Docker version 18.09.0-ce-tp5, build 9eb3d36" 将docker升级到“Doc​​ker版本18.09.0-ce-tp5,构建9eb3d36”后使用ubuntu 18.04

Everything works fine before updating docker 在更新docker之前一切正常

Getting following error on docker-compose up: 在docker-compose上获得以下错误:

ERROR: for mysql_1 Cannot start service mysql: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/242793c2e7ad05e93ccff53ae37e5d8b054a72f9c2076c1b480f33929dbb45aa/log.json: no such file or directory): exec: "docker-runc": executable file not found in $PATH: unknown 错误:for mysql_1无法启动服务mysql:OCI运行时创建失败:无法检索OCI运行时错误(打开/run/containerd/io.containerd.runtime.v1.linux/moby/242793c2e7ad05e93ccff53ae37e5d8b054a72f9c2076c1b480f33929dbb45aa/log.json:没有这样的文件或目录):exec:“docker-runc”:在$ PATH中找不到可执行文件:未知

docker info gives 码头工人信息给出

linux@linux-linux:/$ docker info
Containers: 14
 Running: 14
 Paused: 0
 Stopped: 0
Images: 1091
Server Version: 18.09.0-ce-tp5
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1038
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: containerd runc
Default Runtime: containerd
Init Binary: docker-init
containerd version: ce243288e27971e324363de8f322d221635a8521 (expected: 468a545b9edcd5932818eb9de8e72413e616e86e)
runc version: 1555a78945e56737bc3d15565191d857ee6fa2b9 (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
 apparmor
Kernel Version: 4.15.0-32-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.719GiB
Name: linux-linux
ID: F475:F7JY:3HSG:XLGM:BAPD:CZYD:HRRO:SN3N:SFSX:7XOK:VDZ4:SNMV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

WARNING: No swap limit support

Using ubuntu 18.04 after upgrading docker to "Docker version 18.09.0-ce-tp5, build 9eb3d36" 将docker升级到“Doc​​ker版本18.09.0-ce-tp5,构建9eb3d36”后使用ubuntu 18.04

The TP# releases are pre beta (I suspect it stands for technical preview). TP#版本是预测试版(我怀疑它代表技术预览版)。 These will have issues, and there were lots of changes with the containerd integration. 这些都有问题,容器集成有很多变化。 You can try upgrading to beta1, or go back to the stable 18.06.1 release. 您可以尝试升级到beta1,或者返回稳定的18.06.1版本。 You can see the releases here: 你可以在这里看到版本:

https://github.com/docker/docker-ce/releases https://github.com/docker/docker-ce/releases

Issue: I faced the same issue. 问题:我遇到了同样的问题。

Solution first i restart docker,but when i tried to start my container i was having Error response from daemon: OCI runtime create failed: container with id exists:xxxxxxxxxx 解决方案首先我重新启动docker,但是当我尝试启动我的容器时,我从守护进程获得错误响应:OCI运行时创建失败:存在id的容器:xxxxxxxxxx

but in ps -a it was showing nothing. 但在ps -a中它什么都没显示。 while i was able to run the new container using the same id. 虽然我能够使用相同的ID运行新容器。

than tried reboot my server and it is working fine. 比尝试重新启动我的服务器,它工作正常。

as you can see in this 2 rows: 正如你在这两行中看到的那样:

containerd version: ce243288e27971e324363de8f322d221635a8521 (expected: 468a545b9edcd5932818eb9de8e72413e616e86e)
runc version: 1555a78945e56737bc3d15565191d857ee6fa2b9 (expected: 69663f0bd4b60df09991c08812a60108003fa340)

docker expects another internal container id as the tagged container has. docker期望另一个内部容器ID作为标记容器具有。 i guess this causes the problem. 我想这会导致问题。
have you tried to rebuild your container? 你试过重建你的容器吗?

I faced a similar problem. 我遇到了类似的问题。
Try committing your container. 尝试提交你的容器。
Then run it again. 然后再次运行它。
eg 例如
docker commit RUNNING_CONTAINER IMAGE1 docker commit RUNNING_CONTAINER IMAGE1
docker run -d IMAGE1 docker run -d IMAGE1

service docker restart解决了我的问题

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 exec: \\“mysql\\”: 在 $PATH 中找不到可执行文件": 未知 - exec: \“mysql\”: executable file not found in $PATH": unknown "docker-runc 未安装在系统上" - docker-runc not installed on system OCI 运行时创建失败:runc 创建失败:无法启动容器进程:exec:“split_csv.py”:在 $PATH 中找不到可执行文件:未知 - OCI runtime create failed: runc create failed: unable to start container process: exec: "split_csv.py": executable file not found in $PATH: unknown Docker – exec: "bash": $PATH 中找不到可执行文件 - Docker – exec: "bash": executable file not found in $PATH Docker 撰写:$PATH 中未找到可执行文件:未知 - Docker Compose: executable file not found in $PATH: unknown 以字符串形式运行命令时,Docker exec错误“在$ PATH中找不到可执行文件:未知” - Docker exec error “executable file not found in $PATH”: unknown" when running a command as a string Docker 启动容器进程导致“exec:\\”arg\\“:在 $PATH 中找不到可执行文件”:未知。 - Docker starting container process caused “exec: \”arg\“: executable file not found in $PATH”: unknown. Docker:启动容器进程导致“exec:\”-n\“:$PATH中找不到可执行文件”:未知 - Docker : starting container process caused “exec: \”-n\“: executable file not found in $PATH”: unknown Docker Go 映像:启动容器进程导致:exec:“app”:在 $PATH 中找不到可执行文件:未知 - Docker Go image: starting container process caused: exec: "app": executable file not found in $PATH: unknown 在 $PATH 中找不到 Docker 撰写可执行文件”:未知 - Docker compose executable file not found in $PATH": unknown
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM