CentOS 8上的Docker无法在使用SystemD Ran的Prev容器后启动
尝试使用CentOS 8.5服务器通过服务器测试Docker容器。
该容器中有CentOS 7.9。
它的入口点是/usr/sbin/init。
第一次启动：
Docker Run -name Test -neTwork =主机 - 私人-CAP-ADD CENTOS7_WITH_SBIN_SBIN_INIT
正在通过成功。
之后，尝试启动使用任何Docker图像 -network =主机失败：
docker run -network =主机hello-world
docker: Error response from daemon: failed to create shim: OCI runtime create failed:
container_linux.go:380:
starting container process caused: process_linux.go:402:
getting the final childs pid from pipe caused:
EOF: unknown.
ERRO 0000 error waiting for container: context canceled
我假设启动的第一个容器的Sbin/init入口点， 遵循容器功能的某些断裂， 由于某些损坏了主机Docker Conf conf
由于服务器上的SystemD版本的差异
（CENTOS 8.5）：
systemd 239 (239-51.el8_5.2)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy
在容器上（CentOS 7.9）上，
systemd 219
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
：仅通过重新启动Docker＆amp;容器服务， 我能够再次使用主机网络启动容器。 （直到下次我运行自定义容器。）
有什么想法？ 谢谢
Trying to test docker containers over server with CentOS 8.5 Server.
The container has CentOS 7.9 within it.
Entrypoint for it is /usr/sbin/init.
First launch:
docker run --name test --network=host --privileged --cap-add centos7_with_sbin_init
Is passing success.
After that,trying to launch ANY docker image with
--network=host fails:
docker run -network=host hello-world
docker: Error response from daemon: failed to create shim: OCI runtime create failed:
container_linux.go:380:
starting container process caused: process_linux.go:402:
getting the final childs pid from pipe caused:
EOF: unknown.
ERRO 0000 error waiting for container: context canceled
I assume the sbin/init entrypoint of the 1st container launched,
Some how breaks following container functionality,
By some corruption to undelying host docker conf,
Due to differences in systemd versions
On server (centos 8.5):
systemd 239 (239-51.el8_5.2)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy
On container (centos 7.9):
systemd 219
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
Only by restarting docker & containerd services,
I'm able to launch containers with host network again.
(until next time i run my custom container..)
Any ideas??
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论