According to the github action documentation, we should actually run all actions in containers as the root user - this is the recommended workflow. We originally chose non-root because its standard practice in other docker-based workflows, such as web applications.
Note: GitHub Actions must be run by the default Docker user (root). Ensure your Dockerfile does not set the USER instruction, otherwise you will not be able to access GITHUB_WORKSPACE
Fixes #7
According to the github action documentation, we should actually run all actions in containers as the root user - this is the recommended workflow. We originally chose non-root because its standard practice in other docker-based workflows, such as web applications.
From https://docs.github.com/en/free-pro-team@latest/actions/reference/specifications-for-github-hosted-runners
The above applies to also
GITHUB_ENVandGITHUB_PATH, which are separate paths used by thecore.addPathandcore.setEnvcommands from@actions/core. As of https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - anyone using these containers and those commands have permissions-based failures