简体   繁体   English

Docker 容器启动问题:为 procHooks 进程设置 cgroup 配置导致

[英]Docker container starting issue: setting cgroup config for procHooks process caused

I'm a little newbie to Docker.我是 Docker 的新手。 I was trying to deploying Hortonworks sandbox on docker but unfortunately, the below error encountered.我试图在 docker 上部署 Hortonworks 沙箱,但不幸的是,遇到了以下错误。

docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: resulting devices cgroup与目标模式不匹配:未知。

Once I was able to set up everything on a different server correctly which was a Ubuntu 20.04 VPS from Contabo.一旦我能够在另一台服务器上正确设置所有内容,即来自 Contabo 的 Ubuntu 20.04 VPS。

But this time I have used a VPS from VPSDime and I have tested this on 3 different operating systems and the same error occurred: Ubuntu 20.04, Ubuntu 18.04, CentOS 8.但是这次我使用了来自 VPSDime 的 VPS,并且我在 3 个不同的操作系统上对此进行了测试,并且发生了相同的错误:Ubuntu 20.04、Ubuntu 18.04、ZAA1ZB5720E814BEDA333

Please help me, I have followed this guide here: https://tomas-savenas.medium.com/hortonworks-sandbox-hdp-3-0-on-ubuntu-18-04-using-docker-da579fd654f9请帮助我,我在这里遵循了本指南: https://tomas-savenas.medium.com/hortonworks-sandbox-hdp-3-0-on-ubuntu-18-04-using-docker-da579fd654f9

i had pretty much the same error message with Arch Linux using the old Linux-CK kernel with MuQSS.我使用带有 MuQSS 的旧 Linux-CK kernel 与 Arch Linux 有几乎相同的错误消息。 in my case MuQSS was the rootcause for this error, but I could make it work with the following workaround.在我的情况下,MuQSS 是此错误的根本原因,但我可以使用以下解决方法使其工作。 Add this line to the kernel parameters: systemd.unified_cgroup_hierarchy=0 source: Fix Docker cgroup errors after systemd 248 update将此行添加到 kernel 参数:systemd.unified_cgroup_hierarchy=0 来源: 修复 systemd 248 更新后的 Docker cgroup 错误

暂无
暂无

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

相关问题 对 cgroup 进程的 docker 间歇性故障问题进行故障排除 - Troubleshooting docker intermitted failure issue for cgroup process Docker OCI 运行时创建失败:container_linux.go:349: 启动容器进程导致 - Docker OCI runtime create failed: container_linux.go:349: starting container process caused 运行 docker 容器时出错:启动容器进程导致“exec:\”python\“:在 $PATH 中找不到可执行文件”:未知 - Error running docker container: starting container process caused "exec: \"python\": executable file not found in $PATH": unknown docker-compose oci运行时错误启动容器进程导致对等方重置连接 - docker-compose oci runtime error starting container process caused connection reset by peer docker run 导致启动容器进程导致“exec:\\”./boot.sh\\”:权限被拒绝 - docker run results in starting container process caused "exec: \"./boot.sh\": permission denied 运行 Golang 的 docker 镜像失败,出现错误“启动容器进程导致:exec:“/路径”:权限被拒绝” - Running a docker Image of Golang failed, with error 'starting container process caused: exec: "/path": permission denied' 为什么 docker-compose 失败了? 启动容器进程导致:exec:\"pg_isready -U user - Why docker-compose failed ? starting container process caused: exec: \"pg_isready -U user 错误:启动容器进程导致“exec:\\”/docker-entrypoint.sh\\”:权限被拒绝” - Error: Starting container process caused "exec: \"/docker-entrypoint.sh\": permission denied" 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
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM