You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you using the latest Super-linter version available?
I am using the latest Super-linter version.
I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)
I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.
Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?
I think that this is a Super-linter issue.
Current Behavior
I set FILTER_REGEX_INCLUDE to limit scanning to files in .github/workflows. Checkov is reporting issues on a Dockerfile in the root directory.
Expected Behavior
Checkov should only scan files defined by FILTER_REGEX_INCLUDE.
Super-Linter version
v6.5.1
Relevant log output
CHECKOV
2024-05-29 15:57:00 [INFO] Linting CHECKOV items...
Error: -29 15:57:05 [ERROR] Found errors when linting CHECKOV. Exit code: 1.
2024-05-29 15:57:05 [INFO] Command output for CHECKOV:
------
dockerfile scan results:
Passed checks: 52, Failed checks: 1, Skipped checks: 0
Check: CKV_DOCKER_7: "Ensure the base image uses a non latest version tag"
FAILED for resource: /Dockerfile.FROM
File: /Dockerfile:2-2
Guide: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/docker-policies/docker-policy-index/ensure-the-base-image-uses-a-non-latest-version-tag
2 | FROM ${BASE_IMAGE}
github_actions scan results:
Passed checks: 72, Failed checks: 0, Skipped checks: 0
Steps To Reproduce
step definition:
- name: lint code base
uses: super-linter/super-linter@v6.5.1
env:
DEFAULT_BRANCH: main
FILTER_REGEX_INCLUDE: .*.github/workflows/.*
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# only lint new and modified files
VALIDATE_ALL_CODEBASE: false
Add a Dockerfile with an issue in the root of the repository and run linting
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Are you using the latest Super-linter version available?
I am using the latest Super-linter version.
I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)
I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.
Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?
Current Behavior
I set FILTER_REGEX_INCLUDE to limit scanning to files in .github/workflows. Checkov is reporting issues on a Dockerfile in the root directory.
Expected Behavior
Checkov should only scan files defined by FILTER_REGEX_INCLUDE.
Super-Linter version
Relevant log output
Steps To Reproduce
step definition:
Add a Dockerfile with an issue in the root of the repository and run linting
Anything else?
No response
The text was updated successfully, but these errors were encountered: