podman: [rootless] `podman ps` doesn't show anything, even though container is running (started by systemd service)

Is this a BUG REPORT or FEATURE REQUEST?:

  • kind bug

Description

I have a systemd service, which is enabled, it starts a rootless container. If I ssh into the machine and run podman ps, I get no output, like the container isn’t running. If I do systemctl status unifi, I can clearly see the container is running.

Steps to reproduce the issue:

  1. create a systemd service to start a container, e.g.:
	[Unit]
	Description=UniFi Container
	After=network-online.target
	

	[Service]
	Type=simple
	User=alc
	Group=alc
	ExecStart=/usr/bin/podman start -a unifi-sdn-controller
	ExecStop=/usr/bin/podman stop unifi-sdn-controller
	

	[Install]
	WantedBy=multi-user.target
  1. systemctl enable foobarcontainer.service

  2. reboot

  3. ssh or login at a terminal, and run podman ps, notice it acts as if the container isn’t running.

  4. systemctl status foobarcontainer.service shows it obviously is.

Describe the results you received:

podman ps has no output

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:       0.9.3.1
Go Version:    go1.10.4
OS/Arch:       linux/amd64

Output of podman info:

host:
  Conmon:
    package: podman-0.9.3.1-1.git1cd906d.fc28.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: 3c91f791086f31a0bd68967c7e3c2ad8e06145a6-dirty'
  MemFree: 197369856
  MemTotal: 2077790208
  OCIRuntime:
    package: runc-1.0.0-51.dev.gitfdd8055.fc28.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree: 2211151872
  SwapTotal: 2214588416
  arch: amd64
  cpus: 2
  hostname: atomic.ccbp.online
  kernel: 4.18.11-200.fc28.x86_64
  os: linux
  uptime: 223h 38m 0.68s (Approximately 9.29 days)
insecure registries:
  registries: []
registries:
  registries:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ContainerStore:
    number: 1
  GraphDriverName: vfs
  GraphOptions: []
  GraphRoot: /var/home/alc/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 1
  RunRoot: /run/user/1000/run

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

Fedora Atomic Host 28

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 2
  • Comments: 32 (23 by maintainers)

Most upvoted comments

Hi everyone, I have the same issue on Debian 11 after creating the container with Ansible. The container is running but is not showing either with podman ps or podman ps -all.

Also, when you do, please include the unit file you’re using.