Denied Permission while pulling images

[dipankar-maitra-arch]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
BUG REPORT
/kind bug
Permission Denial
/kind feature
Image Pull
Description

While using podman command - podman pull alpine, getting the following error
Error processing tar file(exit status 1): open /etc/passwd: permission denied
Error: Error committing the finished image: error adding layer with blob "sha256:df9b9388f04ad6279a7410b85cedfdcb2208c0a003da7ab5613af7
1079148139": Error processing tar file(exit status 1): open /etc/passwd: permission denied

Error is same while trying sudo podman pull alpine
However same works when trying using $sudo docker pull alpine

Steps to reproduce the issue:

1. Install podman on Ubuntu

2. podman pull alpine

Describe the results you received:

Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob df9b9388f04a done
Copying config 0ac33e5f5a done
Writing manifest to image destination
Storing signatures
Error processing tar file(exit status 1): open /etc/passwd: permission denied
Error: Error committing the finished image: error adding layer with blob "sha256:df9b9388f04ad6279a7410b85cedfdcb2208c0a003da7ab5613af7
1079148139": Error processing tar file(exit status 1): open /etc/passwd: permission denied

Describe the results you expected:

successful image pull

Additional information you deem important (e.g. issue happens only occasionally):
Ubuntu 18.04 LTS is the OS

Output of podman version:

podman version 3.0.1

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.19.4
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.1.0, commit: '
  cpus: 8
  distribution:
    distribution: ubuntu
    version: "18.04"
  eventLogger: journald
  hostname: AZN-WIDINO-DU02
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
    uidmap:
	 - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
  kernel: 5.4.0-1073-azure
  linkmode: dynamic
  memFree: 544571392
  memTotal: 16786436096
  ociRuntime:
    name: crun
    package: 'crun: /usr/bin/crun'
    path: /usr/bin/crun
    version: |-
      crun version 0.18.1-7931a-dirty
      commit: 7931a1eab0590eff4041c1f74e2844b297c31cea
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP
_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    selinuxEnabled: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.1.8
	  commit: unknown
      libslirp: 4.3.1-git
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.3.1
  swapFree: 0
  swapTotal: 0
  uptime: 170h 36m 20.92s (Approximately 7.08 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /home/wiproadmin/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: vfs
  graphOptions: {}
  graphRoot: /home/admin/.local/share/containers/storage
  graphStatus: {}
  imageStore:
    number: 0
  runRoot: /run/user/1000/containers
  volumePath: /home/admin/.local/share/containers/storage/volumes
version:
  APIVersion: 3.0.0
  Built: 0
  BuiltTime: Thu Jan  1 00:00:00 1970
  GitCommit: ""
  GoVersion: go1.15.2
  OsArch: linux/amd64
   Version: 3.0.1

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

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

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

[mheon]

Any chance you can try with a more recent Podman? 3.0 is very old at this point.

[dipankar-maitra-arch]

I tried this actions/runner-images#4063 (comment) but after all installation, getting the same version for podman i.e., 3.0.1

[rhatdan]

Does it work if you run it as root?

[giuseppe]

what is the underlying file system?

[vrothberg]

Friendly ping, @dipankar-maitra-arch

[vrothberg]

Closing. We can reopen once we know more.