podman: Error: could not get runtime: operation not permitted with stable podman image

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

/kind bug

Description

Using the quay.io/podman/stable image on MacOS or Kubernetes results in Error: could not get runtime: operation not permitted

Steps to reproduce the issue:

  1. Run docker run -it quay.io/podman/stable podman info

Describe the results you received:

Error: could not get runtime: operation not permitted

Describe the results you expected:

It to work

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

It appears to be an issue with the fuse vfs. If I do docker run -it quay.io/podman/stable bash, then execute:

rm -rf /var/lib/shared/overlay-images && rm -rf /var/lib/shared/overlay-layers
rm -rf /var/lib/shared/overlay-images/images.lock /var/lib/shared/overlay-layers/layers.lock
rm -f /etc/containers/storage.conf

Then podman no longer exits with the error.

Output of podman version:

Version:            1.4.2
RemoteAPI Version:  1
Go Version:         go1.12.5
OS/Arch:            linux/amd64

Output of podman info --debug:

$docker run -it quay.io/podman/stable podman --log-level=debug info                                                   
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/lib/containers/storage
DEBU[0000] Using run root /var/run/containers/storage
DEBU[0000] Using static dir /var/lib/containers/storage/libpod
DEBU[0000] Using tmp dir /var/run/libpod
DEBU[0000] Using volume path /var/lib/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: imagestore=/var/lib/shared
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs
ERRO[0000] could not get runtime: operation not permitted

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 24 (16 by maintainers)

Most upvoted comments

We are still working on this. We have gotten it to work, but need to get the container.conf work done to make it a reasonable solution, so that we don’t need to include a huge Command line in podman.

In general, several of us not using systemd would appreciate decoupling.