Original error: CircleCI was unable to start the container because of a userns remapping failure in Docker

Build Environment
#1

Hi
Once trying to use custom created container in my build, I encounter the following error :

CircleCI was unable to start the container because of a userns remapping failure in Docker.

This typically means the image contains files with UID/GID values that are higher than Docker and CircleCI can use.

Checkout our docs Debugging Container ID Cannot Be Mapped to Host ID Error - CircleCI to learn how to fix this problem.
Original error: CircleCI was unable to start the container because of a userns remapping failure in Docker.

This typically means the image contains files with UID/GID values that are higher than Docker and CircleCI can use.

Checkout our docs Debugging Container ID Cannot Be Mapped to Host ID Error - CircleCI to learn how to fix this problem.
Original error: failed to register layer: Error processing tar file(exit status 1): Container ID 101152375
cannot be mapped to a host ID

Note that tried following the link suggestion, yet , NADA!! even tried wider search using:

find / ( -uid +65500 ) -ls 2>/dev/null

Any idea ?
Thx - Albert

#2

That circleci write-up seems to try and make the whole thing more complex than it should be as it is not true to say that the UID/GID is outside of the accepted range. Docker uses UID/GIDs that have the offset to make sure that there are no security issues caused across the system.

You can check the allocated values by

cat /etc/subuid
cat /etc/subgid

There is a slightly different write-up of the issue here

https://jira.atlassian.com/browse/BCLOUD-17319
#3

Hi rit1010
Sorry for the late response. Tried the proposed commands and they result nothing.
Other actions?
Thx