fix: go back to root user in Dockefile

[jmeridth]

Fixes: #101

Pull Request

Proposed Changes

Based on GitHub docs we will not be able to access the workspace of the GitHub Action without being the root user. As a non-root user we won't be able to write to $GITHUB_OUTPUT which is an environment variable that is a path inside the workspace and GitHub Actions using to handle output from the GitHub Action.

Once that was realized, this seems to be the only possible path.

fix: ignore checkov linter requiring user in Dockerfile (docs)

Running checkov locally

Note: CKV_DOCKER_3 is skipped

Check: CKV_DOCKER_3: "Ensure that a user for the container has been created"
	SKIPPED for resource: Dockerfile.
	Suppress comment: No comment provided
	File: Dockerfile:1-24
	Guide: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/docker-policies/docker-policy-index/ensure-that-a-user-for-the-container-has-been-created

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• run make lint and fix any issues that you have introduced
• run make test and ensure you have test coverage for the lines you are introducing

Reviewer

• Label as either bug, documentation, enhancement, infrastructure, or breaking

[jmeridth]

Other options: we do setup a non-root user with sudoer privileges. This should satisfy the security linter and still gives us the same privileges as root in the container. (yep, I understand still insecure)

[zkoppert]

We will likely need to add something in the dockerfile or a config file to exempt the security rule being caught by the linter.

[jmeridth]

@zkoppert updated and pushed with skip for user in Dockerfile

[zkoppert]

Thanks for the follow up on this @jmeridth!