Fix GitHub Actions permission issues by defaulting Dev images to run as the root user #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes: #86
The merge of PR #80 introduced issues with GitHub Actions workflows that rely on the Dev images. GitHub Actions uses a github user to execute commands inside Docker containers. This user typically has a UID/GID of 1001, but it may vary depending on the container configuration.
With the updated CKAN images now running as a non-root user (ckan/ckan-sys with UID/GID 503/502), permission issues can arise during GitHub Actions workflows.
As a temporary workaround, workflows can include an option to run the CKAN container as the root user.
This PR modifies the Dev images to default to running as the root user while preserving the ability to run as a non-root user when needed.