简体   繁体   English

OCI 运行时执行失败:执行失败:container_linux.go:380:启动容器进程导致:执行:<PATH> :

[英]OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: <PATH>:

I've created a astronomer airflow directory home\acoppers\astronomer.我创建了一个天文学家气流目录 home\acoppers\astronomer。 I ran docker db init and docker astro start to get my containers running.我运行 docker db init 和 docker astro start 让我的容器运行。 I want to authenticate my scheduler container to gcloud so I tried the command:我想向 gcloud 验证我的调度程序容器,所以我尝试了以下命令:

docker container exec -it 6903e8589b00 /home/acoppers/google-cloud-sdk/bin/gcloud auth application-default login --no-launch-browser

Since I installed google-cloud-sdk in my home directory.因为我在我的主目录中安装了 google-cloud-sdk。 However I am getting the following error when I run this command:但是,当我运行此命令时出现以下错误:

OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/home/acoppers/google-cloud-sdk/bin/gcloud": stat /home/acoppers/google-cloud-sdk/bin/gcloud: no such file or directory: unknown

Can someone tell me what I am doing wrong?有人可以告诉我我做错了什么吗? Thank you.谢谢你。

Someone might find this useful.有人可能会觉得这很有用。 I was unable exec into the docker container like above.我无法像上面那样执行到 docker 容器中。 I got:我有:

OCI runtime exec failed: exec failed: container_linux.go:380: 
starting container process caused: setup user: no such file or directory: unknown

Turned out - in my case - NodeJS child process caused /dev/null to disappear as soon as I restored it结果 - 在我的情况下 - NodeJS 子进程导致/dev/null在我恢复后立即消失

mknod /dev/null c 1 3
chmod 666 /dev/null

I was able to log in again (tested with two shells one was in the other out)我能够再次登录(用两个外壳测试,一个在另一个外面)

暂无
暂无

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

相关问题 Docker OCI 运行时创建失败:container_linux.go:349: 启动容器进程导致 - Docker OCI runtime create failed: container_linux.go:349: starting container process caused 无法启动服务 prometheus:oci 运行时错误:container_linux.go:235:启动容器进程导致“容器初始化过早退出” - Cannot start service prometheus: oci runtime error: container_linux.go:235: starting container process caused "container init exited prematurely" 启动容器进程导致“exec: &gt; \\”exec\\”:在 $PATH 中找不到可执行文件”:未知 - starting container process caused "exec: > \"exec\": executable file not found in $PATH": unknown 启动容器过程导致“ exec:\\\\” tail -f / dev / null \\\\”:统计信息尾巴-f / dev / null:无此类文件或目录 - Starting container process caused “exec: \\”tail -f /dev/null\\": stat tail -f /dev/null: no such file or directory docker exec:rpc错误:code = 2 desc = oci运行时错误:exec失败 - docker exec: rpc error: code = 2 desc = oci runtime error: exec failed Docker:standard_init_linux.go:211:exec 用户进程导致“exec 格式错误” - Docker: standard_init_linux.go:211: exec user process caused "exec format error" Docker - standard_init_linux.go:211:执行用户进程导致“执行格式错误”覆盆子 - Docker - standard_init_linux.go:211: exec user process caused “exec format error” raspberry 错误:standard_init_linux.go:228:导致执行用户进程:执行格式错误 - Error : standard_init_linux.go:228: exec user process caused: exec format error standard_init_linux.go:178:执行用户进程导致“执行格式错误” - standard_init_linux.go:178: exec user process caused "exec format error" 树莓派 docker 错误:standard_init_linux.go:178:exec 用户进程导致“exec 格式错误” - Raspberry-pi docker error: standard_init_linux.go:178: exec user process caused “exec format error”
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM