Bump node from 20-bullseye to 23-bullseye #199
Annotations
11 warnings
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
run kics Scan:
Dockerfile#L64
A user should be specified in the dockerfile, otherwise the image will run as root
|
|
run kics Scan:
Dockerfile#L47
When installing a package, its pin version should be defined
|
|
run kics Scan:
Dockerfile#L20
It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only execution permissions are required on the file, not ownership
|
|
run kics Scan:
Dockerfile#L70
It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only execution permissions are required on the file, not ownership
|
|
run kics Scan:
Dockerfile#L71
It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only execution permissions are required on the file, not ownership
|
|
run kics Scan:
Dockerfile#L64
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working
|
|
run kics Scan:
.github/workflows/docker-image.yml#L67
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|
|
run kics Scan:
.github/workflows/docker-image.yml#L47
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
|
|
run kics Scan:
Dockerfile#L47
Check if any apt-get installs don't use '--no-install-recommends' flag to avoid installing additional packages.
|
|
run kics Scan:
Dockerfile#L47
After using apt-get install, it is needed to delete apt-get lists
|
Loading