mount callback failed on high UID files

When base image have file with high UID/GID, buildkit (rootless) return with those error

15:35:31  #5 [1/6] FROM docker-registry.local/infrastructure-python-builder:master-latest@sha256:2847172932d81865058e7cc8902bb1323e23d1730e67f7a5f3c1d5577f0e109b
15:35:31  #5 CACHED
15:35:31  
15:35:31  #4 [internal] load build context
15:35:31  #4 transferring context: 720.00kB 0.0s done
15:35:31  #4 DONE 0.0s
15:35:31  
15:35:31  #7 [2/6] RUN pyenv local system $(pyenv versions --bare)
15:35:31  #7 ERROR: mount callback failed on /run/user/1000/containerd-mount2889517150: lchown /run/user/1000/containerd-mount2889517150/etc/poetry/lib/poetry/_vendor/py2.7/backports/entry_points_selectable.py: invalid argument

Inside based image

ls -l /etc/poetry/lib/poetry/_vendor/py2.7/backports/
total 16
drwxr-xr-x 2 root       root       4096 Apr 14 14:02 configparser
-rw-r--r-- 1 1407182137 1059092950 7444 Aug 19  2021 entry_points_selectable.py
-rw-r--r-- 1 root       root        212 Aug 19  2021 __init__.py

The report provides no source file or test; begin by reproducing the rootless build with the shown base image and the high-UID/GID file, then inspect the mount callback failure. Done means a rootless build handles those files without the lchown invalid-argument error.