potentially insufficient UIDs or GIDs available in user namespace

[cmoulliard]

Issue

During the execution of the buildah bud executable to create an image, then this error is reported due to:

insufficient UIDs or GIDs available in user namespace (requested 65532:65532 for /home): Check /etc/subuid and /etc/subgid: lchown /home: invalid argument

Log

## Execute buildah bud
time="2021-10-27T14:21:53Z" level=warning msg="Reading allowed ID mappings: Reading subuid mappings for user \"jboss\" and subgid mappings for group \"jboss\": No subuid ranges found for user \"jboss\" in /etc/subuid"
time="2021-10-27T14:21:53Z" level=warning msg="Found no UID ranges set aside for user \"jboss\" in /etc/subuid."
time="2021-10-27T14:21:53Z" level=warning msg="Found no GID ranges set aside for user \"jboss\" in /etc/subgid."
time="2021-10-27T14:21:53Z" level=info msg="WORKSPACE DIR: %!(EXTRA string=/workspace)"
time="2021-10-27T14:21:53Z" level=info msg="Buildah tempdir : %!(EXTRA string=/workspace/buildah-poc-4022538008)"
time="2021-10-27T14:21:53Z" level=info msg="Dockerfile : %!(EXTRA string=/workspace/Dockerfile)"
time="2021-10-27T14:21:55Z" level=error msg="While applying layer: ApplyLayer exit status 1 stdout:  stderr: potentially insufficient UIDs or GIDs available in user namespace (requested 65532:65532 for /home): Check /etc/subuid and /etc/subgid: lchown /home: invalid argument"
time="2021-10-27T14:21:55Z" level=error msg="Build image failed: %!(EXTRA string=error creating build container: writing blob: adding layer with blob \"sha256:6b34ec2e9eccc9677a49a03354553a2be0694bb8c26a282ff3783aa134255ee1\": ApplyLayer exit status 1 stdout:  stderr: potentially insufficient UIDs or GIDs available in user namespace (requested 65532:65532 for /home): Check /etc/subuid and /etc/subgid: lchown /home: invalid argument)"
time="2021-10-27T14:21:55Z" level=info msg="Image id: %!(EXTRA string=)"

How to reproduce

• Have access to a k8s cluster (e.g kind create cluster)
• Deploy the poc on k8s : kubectl apply -f k8s/manifest.yml
• Check the log of the initcontainer