CircleCI-Public / GitHub-Super-Linter-Orb

A CircleCI Orb implementation of GitHub's SuperLinter. Run multiple linters in your CI pipeline at once.
https://circleci.com/developer/orbs/orb/circleci/github-super-linter
MIT License
2 stars 7 forks source link

Default v4 tag causing spin up step error #8

Open imlogang opened 1 year ago

imlogang commented 1 year ago

Orb version:

circleci/github-super-linter@1.0.1

What happened:

The default v4 tag is throwing an 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 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.

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: failed to register layer: Error processing tar file(exit status 1): Container ID 369884941 cannot be mapped to a host ID

Expected behavior:

The orb starts the job without error.

Additional Information:

The v4 tag has seen multiple updates. Changing to v4.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

naynivek commented 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.