[英]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.