Thanks! I dived into the issue a bit more, and it seems like the problem lies in the default mapping in /etc/subuid file.

The first OS regular user created usually has the assignment 100000:65536 in /etc/subuid.
I decided to assign the values (231072:65536) from the user that succeed with the podman pull command to the user with previous 100000:65536. With the new values, podman (and therefore, clickman) runs without issues.

I don't see any conflict on the default range assigned, but definitely that new assignment seems to fix it.

Hope it helps for those that run into it

@Vlad-Nirky Good morning! I ran into the same issue.

It seems to be related to the running user environment. With my current user, I try multiple combinations, userns and userid/groupid mappings with no luck.

Finally I decided to try podman pulling directly the image with other user and it went just fine. It worked both for root and rootless installations.

$ podman run  --name ubuntutouch docker://clickable/amd64-ut24.04-1.x-amd64:latest

It does not seem to be an issue with clickable. I'm using the python package clickable-ut.