简体   繁体   English

kubernetes 中的奇怪错误:“启动容器进程导致”exec:\“/usr/bin/dumb-init\”:stat /usr/bin/dumb-init:没有这样的文件或目录”

[英]Weird Error in kubernetes: “starting container process caused ”exec: \“/usr/bin/dumb-init\”: stat /usr/bin/dumb-init: no such file or directory"

I built a customised Docker image of airflow following this document: " https://github.com/puckel/docker-airflow ".我在此文档之后构建了 airflow 的自定义 Docker 映像:“ https://github.com/puckel/docker-airflow ”。 Built and run in my local VM.在我的本地 VM 中构建并运行。 Everything was successful and airflow was up.一切都成功了,airflow 起来了。 Pushed the image to ACR (Azure container registry) and launched it in aks via stable helm chart.将映像推送到 ACR(Azure 容器注册表)并通过稳定的 helm chart 在 aks 中启动它。 Referred this link " https://github.com/helm/charts/tree/master/stable/airflow ".参考此链接“ https://github.com/helm/charts/tree/master/stable/airflow ”。 Now suddenly in kubernetes the pods are not up and fails out with the below error.现在突然在 kubernetes 中,吊舱没有启动并出现以下错误。

Error: failed to start container "airflow-scheduler": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory": unknown
Back-off restarting failed container

The most weird part of this error was I was able to do this till the previous day without any issues.这个错误最奇怪的部分是我能够做到这一点,直到前一天没有任何问题。 Suddenly today this error pops in AKS alone.今天突然间,这个错误仅在 AKS 中出现。 It runs fine in my local VM too successfully.它在我的本地虚拟机中运行得也很成功。 Have anyone experienced this before?以前有人经历过吗?

PS for those who don't know the stable chart has an option to give our custom image URL in the values.yaml file. PS 对于那些不知道稳定图表的人,可以选择在 values.yaml 文件中提供我们的自定义图像 URL。 I'm also using the same method to deploy my image.我也使用相同的方法来部署我的图像。

Found out what issue was.找出了什么问题。 stable/airflow chart had made a massive update to 7.0.1 and one of those changes involves not supporting puckel-docker image anymore and will support only apache's official docker image going forward.稳定/气流图表对 7.0.1 进行了大规模更新,其中一项更改涉及不再支持 puckel-docker 映像,并且将仅支持 apache 的官方 docker 映像。 Can look at this issue to get an insight https://github.com/helm/charts/issues/22483可以看这个issue来了解https://github.com/helm/charts/issues/22483

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

相关问题 启动容器进程导致:exec: "/bin/sh": stat /bin/sh: no such file or directory ---- executor failed running [/bin/sh -c - starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory ---- executor failed running [/bin/sh -c /usr/bin/jekyll: 没有那个文件或目录 - /usr/bin/jekyll: No such file or directory /usr/bin/time: 没有那个文件或目录 - /usr/bin/time: No such file or directory /usr/bin/bash: 没有这样的文件或目录 - /usr/bin/bash: No such file or directory / usr / bin / java:是一个目录 - /usr/bin/java: is a directory 启动容器过程导致“ 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 gradlew 错误:/usr/bin/env: bash: No such file or directory - Error with gradlew: /usr/bin/env: bash: No such file or directory 无法执行/ usr / bin / qmicli:没有这样的文件或目录 - unable to execute /usr/bin/qmicli: No such file or directory / usr / local / bin / qtpasswd:没有这样的文件或目录 - /usr/local/bin/qtpasswd: No such file or directory ruby:usr / bin / environment ruby​​没有这样的文件或目录 - ruby: usr/bin/environment ruby no such file or directory
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM