podman 无法刷新容器
最近对我的 rehel 8 进行了 podman 3.4.2 更新后，我的 pod 中的容器（包括 pod 本身）在近 2 小时后退出。
我的操作系统：
$hostnamectl
Static hostname: DELL
Icon name: computer-server
Chassis: server
Machine ID: 1d0417c6b545caa9f12c94566
Boot ID: 24f34ee54545w71c01c55c
Operating System: Red Hat Enterprise Linux 8.5 (Ootpa)
CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
Kernel: Linux 4.18.0-348.12.2.el8_5.x86_64
Architecture: x86-64
ERRO[0000] Error refreshing container 0beda9a50c18fbc193ec2249bdd76afbe07171df35ace5dd9d47c929ebec682d: error acquiring lock 1 for container 0beda9a50c18fbc193ec2249bdd76afbe07171df35ace5dd9d47c929ebec682d: file exists
ERRO[0000] Error refreshing container 48329370f65d11178e715c2a065d8ca8883bcfc7961460be3e10a5bf02eb5292: error acquiring lock 3 for container 48329370f65d11178e715c2a065d8ca8883bcfc7961460be3e10a5bf02eb5292: file exists
ERRO[0000] Error refreshing container fee25dccc31d0fd771a3cc7afcee857c0c0f33af1f7166287a4d8108b7a7605f: error acquiring lock 2 for container fee25dccc31d0fd771a3cc7afcee857c0c0f33af1f7166287a4d8108b7a7605f: file exists
ERRO[0000] Error refreshing pod 094bfe200b1c9afd9f297facec49f0da40f73e9eb049c339827b2fee10686388: error retrieving lock 0 for pod 094bfe200b1c9afd9f297facec49f0da40f73e9eb049c339827b2fee10686388: file exists
更新 当我从使用 rootless 用户登录的服务器注销时，就会出现问题！
After a recent update on my rehel 8 with podman 3.4.2 on it my containers in a pod including the pod itself are exiting after almost 2 hours.
My OS:
$hostnamectl
Static hostname: DELL
Icon name: computer-server
Chassis: server
Machine ID: 1d0417c6b545caa9f12c94566
Boot ID: 24f34ee54545w71c01c55c
Operating System: Red Hat Enterprise Linux 8.5 (Ootpa)
CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
Kernel: Linux 4.18.0-348.12.2.el8_5.x86_64
Architecture: x86-64
ERRO[0000] Error refreshing container 0beda9a50c18fbc193ec2249bdd76afbe07171df35ace5dd9d47c929ebec682d: error acquiring lock 1 for container 0beda9a50c18fbc193ec2249bdd76afbe07171df35ace5dd9d47c929ebec682d: file exists
ERRO[0000] Error refreshing container 48329370f65d11178e715c2a065d8ca8883bcfc7961460be3e10a5bf02eb5292: error acquiring lock 3 for container 48329370f65d11178e715c2a065d8ca8883bcfc7961460be3e10a5bf02eb5292: file exists
ERRO[0000] Error refreshing container fee25dccc31d0fd771a3cc7afcee857c0c0f33af1f7166287a4d8108b7a7605f: error acquiring lock 2 for container fee25dccc31d0fd771a3cc7afcee857c0c0f33af1f7166287a4d8108b7a7605f: file exists
ERRO[0000] Error refreshing pod 094bfe200b1c9afd9f297facec49f0da40f73e9eb049c339827b2fee10686388: error retrieving lock 0 for pod 094bfe200b1c9afd9f297facec49f0da40f73e9eb049c339827b2fee10686388: file exists
UPDATE
The problem occures when I log out from the server on which I am loged in with the rootless user!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
该问题已通过运行解决：loginctl enable-linger $user
如 https://www.reddit.com/r/podman/ 中所述评论/h00nfi/rootless_systemd_restarting_containers_when_i_log/
The problem has benn solved by running : loginctl enable-linger $user
as described in https://www.reddit.com/r/podman/comments/h00nfi/rootless_systemd_restarting_containers_when_i_log/