feat(docker/no-driver/Dockerfile.no-falcoctl-distroless): Provide distroless falco image without falcoctl #3176
+53
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This PR introduces a new Docker image that builds the Falco application without falcoctl present in said image. People could build Falco using this Docker image if they are operating Falco in a sensitive environment or just don't want/need falcoctl. This proposed Dockerfile can also reduce the attack surface introduced by falcoctl in the Falco image.
Which issue(s) this PR fixes:
Related to points made in #3165
Special notes for your reviewer:
After reading through #3165 I noticed that there is a proposal to depreciate the Falco distroless image. I figured I would open this PR anyway to help with the dev work / show that there is interest in having a Falco image that does not contain falcoctl.
Does this PR introduce a user-facing change?: