Disable / ignore suibuid error when ignore_chown_error is set

[snowhanse]

Issue Description

podman --version
podman version 1.6.4

When setting the option storage.options.ignore_chown_errors = "true" in storage.conf, subuid are no longer required.
However, podman still produce an error message on podman run which is misleading, and gives the incorrect impression that it may be involved with or be the root cause of any other issues that may be present, and at best send folks on a wild goose chase when there are issues arise.

In other words, when ignore_chown_errors is explicitly set to true, presence in /etc/subuid should be seen as expected rather than an error

$ podman run  fedora echo hi
ERRO[0000] cannot find mappings for user hanskristian.moen: No subuid ranges found for user "hanskristian.moen" in /etc/subuid
hi

Steps to reproduce the issue

Steps to reproduce the issue

1. update ~/.config/containers/storage.conf for a user with no entry in /etc/subuid with

   [storage.options]
       ignore_chown_errors = "true"
   

2. Execute podman run fedora echo hi

Describe the results you received

Observed misleading error message

$ podman run  fedora echo hi
ERRO[0000] cannot find mappings for user hanskristian.moen: No subuid ranges found for user "hanskristian.moen" in /etc/subuid
hi

Describe the results you expected

No errors present

$ podman run  fedora echo hi
hi

podman info output

$ podman info
ERRO[0000] cannot find mappings for user hanskristian.moen: No subuid ranges found for user "hanskristian.moen" in /etc/subuid
host:
  BuildahVersion: 1.11.7
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.8-1.el7.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.8, commit: f85c8b1ce77b73bcd48b2d802396321217008762'
  Distribution:
    distribution: '"centos"'
    version: "7"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 669
      size: 1
    uidmap:
    - container_id: 0
      host_id: 73170
      size: 1
  MemFree: 756174848
  MemTotal: 16656695296
  OCIRuntime:
    name: runc
    package: containerd.io-1.6.22-3.1.el7.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.1.8
      commit: v1.1.8-0-g82f18fe
      spec: 1.0.2-dev
      go: go1.19.11
      libseccomp: 2.3.1
  SwapFree: 2142236672
  SwapTotal: 2147479552
  arch: amd64
  cpus: 4
  eventlogger: file
  hostname: ******
  kernel: 3.10.0-1160.95.1.el7.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.3-4.el7_8.x86_64
    Version: |-
      slirp4netns version 0.4.3
      commit: 2244b9b6461afeccad1678fac3d6e478c28b4ad6
  uptime: 2209h 42m 46.4s (Approximately 92.04 days)
registries:
  blocked: null
  insecure: null
  search:
  - registry.access.redhat.com
  - registry.redhat.io
  - docker.io
store:
  ConfigFile: /home/users/hanskristian.moen/.config/containers/storage.conf
  ContainerStore:
    number: 14
  GraphDriverName: overlay
  GraphOptions:
    overlay.ignore_chown_errors: "true"
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.2-6.el7_8.x86_64
      Version: |-
        fuse-overlayfs: version 0.7.2
        FUSE library version 3.6.1
        using FUSE kernel interface version 7.29
  GraphRoot: /home/users/hanskristian.moen/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 3
  RunRoot: /tmp/run-73170/containers
  VolumePath: /home/users/hanskristian.moen/.local/share/containers/storage/volumes

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

No

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[rhatdan]

Interested in opening a PR to fix?

@giuseppe WDYT?

[giuseppe]

can you please try with a newer version of podman?

[baude]

@snowhanse could you please try with the latest version of podman ... 4.8.2 ... podman 1.6 is well out of our fair upstream support window.

[snowhanse]

doing a quick test with 5.0.0-dev-702c6f8ad it seems at least in this it does not appear. So it seems to have been fixed somewhere between these version. I'll close this and get us up on a more recent version