podman: rootless podman fails to run after system reboot

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

We are running our pod using systemctl --user start pod-appd.service after the system reboot. none of the podman commands working. its hang.

Steps to reproduce the issue:

  1. mkdir -p ~/.config/systemd/user

  2. podman generate systemd --files --restart-policy=always --name appd

  3. cp .service /home/podman/.config/systemd/user

  4. systemctl --user daemon-reload

  5. systemctl --user enable pod-appd.service

  6. systemctl --user start pod-appd.service

  7. loginctl enable-linger podman

Describe the results you received: after the system reboot none of the podman commands are working other than podman version.

Describe the results you expected: The pod & containers should have started and all podman commands should work

Additional information you deem important (e.g. issue happens only occasionally): Initially in that instance I got Failed to connect to bus: No such file or directory error for systemctl --user. So I added export XDG_RUNTIME=/run/user/$(id -u) in /home/podman/.bashrc` file.

Output of podman version:

Version:            1.6.4
RemoteAPI Version:  1
Go Version:         go1.13.4
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.13.4
  podman version: 1.6.4
host:
  BuildahVersion: 1.12.0-dev
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.6-1.module+el8.2.0+6369+1f4293b4.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.6, commit: e33ff1d39b97fdec3963b8ae6621e2a235c1ac17'
  Distribution:
    distribution: '"rhel"'
    version: "8.2"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 600000
      size: 1
    - container_id: 1
      host_id: 666666
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 600000
      size: 1
    - container_id: 1
      host_id: 666666
      size: 65536
  MemFree: 141611008
  MemTotal: 8189214720
  OCIRuntime:
    name: runc
    package: runc-1.0.0-64.rc10.module+el8.2.0+6369+1f4293b4.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree: 2012213248
  SwapTotal: 2097147904
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: uklvadsb0411
  kernel: 4.18.0-193.14.3.el8_2.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.2-3.git21fdece.module+el8.2.0+6369+1f4293b4.x86_64
    Version: |-
      slirp4netns version 0.4.2+dev
      commit: 21fdece2737dc24ffa3f01a341b8a6854f8b13b4
  uptime: 356h 18m 10.28s (Approximately 14.83 days)
registries:
  blocked:
  - all
  insecure: null
  search:
  - artifactory.global.com
  - prod.artifactory.global.com
store:
  ConfigFile: /home/podman/.config/containers/storage.conf
  ContainerStore:
    number: 0
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.2-5.module+el8.2.0+6369+1f4293b4.x86_64
      Version: |-
        fuse-overlayfs: version 0.7.2
        FUSE library version 3.2.1
        using FUSE kernel interface version 7.26
  GraphRoot: /home/podman/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 0
  RunRoot: /run/user/600000
  VolumePath: /home/podman/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.6.4-15.module+el8.2.0+7290+954fb593.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes its working in podman 1.9.3 version

Additional environment details (AWS, VirtualBox, physical, etc.): VirtualBox

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 32 (13 by maintainers)

Most upvoted comments

you might be hitting https://github.com/containers/podman/issues/5423 that is fixed in v1.9.3