Failed to build on archlinux via podman

As per: https://doc.redox-os.org/book/ch02-06-podman-build.html#new-working-directory I did:

curl -sf https://gitlab.redox-os.org/redox-os/redox/raw/master/podman_bootstrap.sh -o podman_bootstrap.sh
time bash -e podman_bootstrap.sh
cd redox
make all

And then got the following:

rukai@memes redox$ make all
rm -f build/container.tag
If podman_home dir cannot be removed, remove with "sudo rm".
rm -rf /home/rukai2/Projects/Crates/redox/foo/redox/build/podman || true
podman image rm --force redox-base || true
ERRO[0000] cannot find UID/GID for user rukai: no subuid ranges found for user "rukai" in /etc/subuid - check rootless mode in man pages. 
WARN[0000] Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user 
mkdir -p /home/rukai2/Projects/Crates/redox/foo/redox/build/podman
Building Podman image. This may take some time.
sed s/_UID_/`id -u`/ podman/redox-base-containerfile | podman build --file - --volume /home/rukai2/Projects/Crates/redox/foo/redox:/mnt/redox:Z --volume /home/rukai2/Projects/Crates/redox/foo/redox/build/podman:/home:Z --tag redox-base
STEP 1/3: FROM ubuntu:latest
Resolved "ubuntu" as an alias (/etc/containers/registries.conf.d/00-shortnames.conf)
Trying to pull docker.io/library/ubuntu:latest...
Getting image source signatures
Copying blob aece8493d397 done   | 
Error: creating build container: copying system image from manifest list: writing blob: adding layer with blob "sha256:aece8493d3972efa43bfd4ee3cdba659c0f787f8f59c82fb3e48c87cbb22a12e": processing tar file(potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run "podman system migrate": lchown /etc/gshadow: invalid argument): exit status 1
make: *** [mk/podman.mk:57: build/container.tag] Error 1

I also got this issue when following: https://doc.redox-os.org/book/ch02-06-podman-build.html#existing-working-directory I tried that originally before trying the from new working directory build.