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"

问题描述

我遵循此文档构建了一个自定义的气流Docker镜像:" https://github.com/puckel/docker-airflow ".在我的本地VM中构建并运行.一切都成功了，气流增加了.将图像推送到ACR(Azure容器注册表)，并通过稳定的Helm图表将其启动.引用此链接" https://github.com/helm/charts/tree/主/稳定/气流".现在突然在kubernetes中，豆荚没有启动，并因以下错误而失败.

I built a customised Docker image of airflow following this document: "https://github.com/puckel/docker-airflow". Built and run in my local VM. Everything was successful and airflow was up. Pushed the image to ACR (Azure container registry) and launched it in aks via stable helm chart. Referred this link "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.

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

此错误最奇怪的部分是我能够做到这一点，直到前一天没有任何问题.今天突然，此错误仅在AKS中弹出.它在我的本地VM中也运行得很好.以前有没有人经历过?

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. It runs fine in my local VM too successfully. Have anyone experienced this before?

P.S.对于那些不知道稳定图表的用户，可以选择在values.yaml文件中提供我们的自定义图像网址.我也使用相同的方法来部署映像.

P.S. for those who don't know the stable chart has an option to give our custom image URL in the values.yaml file. I'm also using the same method to deploy my image.

推荐答案

找出了什么问题.稳定/气流图已对7.0.1进行了大量更新，其中一项更改涉及不再支持puckel-docker映像，并且将仅支持apache的官方docker映像.可以看一下这个问题来获得见识 https://github.com/helm/charts/issues/22483

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. Can look at this issue to get an insight https://github.com/helm/charts/issues/22483

这篇关于kubernetes中的怪异错误:“启动容器进程导致了"exec:\"/usr/bin/dumb-init \":stat/usr/bin/dumb-init:无此类文件或目录"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！