• 【Linux】Rocky 9.0 Podman服务无法正常启动

            Rocky Linux 9.0发布后，我在本地虚拟机对该版本进行了安装和测试，发现Podman服务在某些情况下，无法正常启动。

            当/etc/selinux/config配置中，SELINUX=enforcing为默认配置的时候，启动Podman服务，会出现下面的报错。

    1. [root@rocky-9 ~]# systemctl status podman.service 
    2. × podman.service - Podman API Service
    3.      Loaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor preset: disabled)
    4.      Active: failed (Result: exit-code) since Wed 2022-08-31 22:34:44 CST; 3min 44s ago
    5. TriggeredBy: ● podman.socket
    6.        Docs: man:podman-system-service(1)
    7.     Process: 1675 ExecStart=/usr/bin/podman $LOGGING system service (code=exited, status=125)
    8.    Main PID: 1675 (code=exited, status=125)
    9.         CPU: 83ms
    10.  
    11. 8月 31 22:34:44 rocky-9.0 systemd[1]: Starting Podman API Service...
    12. 8月 31 22:34:44 rocky-9.0 systemd[1]: Started Podman API Service.
    13. 8月 31 22:34:44 rocky-9.0 podman[1675]: time="2022-08-31T22:34:44+08:00" level=info msg="/usr/bin/podman filtering at log level info"
    14. 8月 31 22:34:44 rocky-9.0 podman[1675]: time="2022-08-31T22:34:44+08:00" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY>
    15. 8月 31 22:34:44 rocky-9.0 podman[1675]: Error: error opening "/etc/cni/net.d/cni.lock": permission denied
    16. 8月 31 22:34:44 rocky-9.0 systemd[1]: podman.service: Main process exited, code=exited, status=125/n/a
    17. 8月 31 22:34:44 rocky-9.0 systemd[1]: podman.service: Failed with result 'exit-code'.

    发现此问题后，我第一时间上报问题到社区论坛

            从官方技术人员给的回复来看，是selinux导致了上面问题的出现，并且说这个问题可以通过更新container-selinux到2.179版本来解决。

            但是，时隔一个多月后，我再次测试，并将container-selinux升级到了2.189版本，此问题仍未能解决。

    1. [root@rocky-9 ~]# rpm -qa container-selinux
    2. container-selinux-2.189.0-1.el9.noarch
    3.  
    4. [root@rocky-9 net.d]# systemctl status podman.service
    5. ● podman.service - Podman API Service
    6.      Loaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor
    7. preset: disabled)
    8.      Active: active (running) since Wed 2022-08-31 16:33:33 CST; 1ms ago
    9. TriggeredBy: ● podman.socket
    10.        Docs: man:podman-system-service(1)
    11.    Main PID: 45751 (podman)
    12.       Tasks: 1 (limit: 50279)
    13.      Memory: 492.0K
    14.         CPU: 2ms
    15.      CGroup: /system.slice/podman.service
    16.              └─45751 /usr/bin/podman --log-level=info system service
    17.  
    18. 8月 31 16:33:33 rocky-9.0 systemd[1]: Starting Podman API Service...
    19. 8月 31 16:33:33 rocky-9.0 systemd[1]: Started Podman API Service.
    20.  
    21. [root@rocky-9 net.d]# systemctl status podman.service
    22. ● podman.service - Podman API Service
    23.      Loaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor
    24. preset: disabled)
    25.      Active: active (running) since Wed 2022-08-31 16:33:50 CST; 243ms ago
    26. TriggeredBy: ● podman.socket
    27.        Docs: man:podman-system-service(1)
    28.    Main PID: 47014
    29.       Tasks: 2 (limit: 50279)
    30.      Memory: 23.3M
    31.         CPU: 272ms
    32.      CGroup: /system.slice/podman.service
    33.  
    34. 8月 31 16:33:50 rocky-9.0 systemd[1]: podman.service: Failed with result
    35. 'exit-code'.
    36. 8月 31 16:33:50 rocky-9.0 systemd[1]: Starting Podman API Service...
    37. 8月 31 16:33:50 rocky-9.0 systemd[1]: Started Podman API Service.
    38. 8月 31 16:33:50 rocky-9.0 podman[47014]: time="2022-08-31T16:33:50+08:00"
    39. level=info msg="/usr/bin/podman filtering at log level info"
    40. 8月 31 16:33:50 rocky-9.0 podman[47014]: time="2022-08-31T16:33:50+08:00"
    41. level=info msg="Not using native diff for overlay, this may cause degraded
    42. performance for building images: kernel has CONFIG_OVERLA>
    43. 8月 31 16:33:50 rocky-9.0 podman[47014]: Error: error opening
    44. "/etc/cni/net.d/cni.lock": permission denied
    45. 8月 31 16:33:50 rocky-9.0 systemd[1]: podman.service: Main process exited,
    46. code=exited, status=125/n/a
    47. 8月 31 16:33:50 rocky-9.0 systemd[1]: podman.service: Failed with result
    48. 'exit-code'.

     目前，此问题只能通过将selinux设置为SELINUX=disabled，并重启系统的方式，才能暂时解决。

    1. [root@rocky-9 ~]# systemctl status podman.service podman.socket
    2. ● podman.service - Podman API Service
    3.      Loaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor preset: disabled)
    4.      Active: active (running) since Wed 2022-08-31 22:52:30 CST; 1min 15s ago
    5. TriggeredBy: ● podman.socket
    6.        Docs: man:podman-system-service(1)
    7.    Main PID: 2161 (podman)
    8.       Tasks: 12 (limit: 50279)
    9.      Memory: 40.7M
    10.         CPU: 693ms
    11.      CGroup: /system.slice/podman.service
    12.              └─2161 /usr/bin/podman --log-level=info system service
    13.  
    14. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/json?all=true HTTP/1.1" 200 1189 "" ""
    15. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/json?all=true&filters=%7B%22id%22%3A%5B%22fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c>
    16. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/json?all=true&filters=%7B%22id%22%3A%5B%22fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c>
    17. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309/json?size=false HTTP/1.1" 200 6637 ">
    18. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309/json?size=false HTTP/1.1" 200 6637 ">
    19. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309/json?size=false HTTP/1.1" 200 6637 ">
    20. 8月 31 22:53:12 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:12 +0800] "GET /v1.12/libpod/containers/fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309/json?size=false HTTP/1.1" 200 6637 ">
    21. 8月 31 22:53:19 rocky-9.0 podman[2161]: 2022-08-31 22:53:19.77482043 +0800 CST m=+49.272022630 container remove fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309 (image=localhost/tomcat-rocky>
    22. 8月 31 22:53:19 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:19 +0800] "DELETE /v1.12/libpod/containers/fc733bd336856e86c4a8944e902cae0b36877511a674612807d5ca5e05c65309?force=false HTTP/1.1" 200 76 "" ""
    23. 8月 31 22:53:20 rocky-9.0 podman[2161]: @ - - [31/Aug/2022:22:53:20 +0800] "GET /v1.12/libpod/containers/json?all=true HTTP/1.1" 200 3 "" ""
    24.  
    25. ● podman.socket - Podman API Socket
    26.      Loaded: loaded (/usr/lib/systemd/system/podman.socket; enabled; vendor preset: disabled)
    27.      Active: active (running) since Wed 2022-08-31 22:51:24 CST; 2min 21s ago
    28.       Until: Wed 2022-08-31 22:51:24 CST; 2min 21s ago
    29.    Triggers: ● podman.service
    30.        Docs: man:podman-system-service(1)
    31.      Listen: /run/podman/podman.sock (Stream)
    32.      CGroup: /system.slice/podman.socket
    33.  
    34. 8月 31 22:51:24 rocky-9.0 systemd[1]: Listening on Podman API Socket.

            这时，在Rocky Linux 9的可视化管理后台中，就可以正常使用Podman来下载镜像和运行容器实例了。

  • 相关阅读:
    ModStart - 模块化开发框架的引领者
    深度测评FL Studio性能，多年Fl Studio使用感受分享
    第五章 循环结构程序设计
    ptables基本语法使用规则
    Golang每日一题
    Hive基础教程
    leetcode链表系列(环形链表篇)
    Ubuntu 20系统WIFI断连问题
    GoLang开发使用gin框架搭建web程序
    通过idea实现springboot集成mybatys
  • 原文地址：https://blog.csdn.net/cnskylee/article/details/126623492