Open imlogang opened 1 year ago
Hi, I tried with the version: v4.10.1, same behavior.
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 https://circleci.com/docs/2.0/high-uid-error/ to learn how to fix this problem.
Original error: CircleCI was unable to start the container because of a userns remapping failure in Docker.
Orb version:
circleci/github-super-linter@1.0.1
What happened:
The default
v4
tag is throwing an error:Expected behavior:
The orb starts the job without error.
Additional Information:
The
v4
tag has seen multiple updates. Changing tov4.9.0
, which aligns with the latest release for this orb, allows it to start, but is ~1 year old. https://hub.docker.com/layers/github/super-linter/v4.9.0/images/sha256-a39073f3991044b0f0280e2eab2ff489ee62005c06d2ccc3c33d05a6b0cf1680?context=explore