-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run as non-root/Use the same UID and GID as the GitHub runners? #18
Comments
Hello! It is actually a requirement to have a published action uses the default Docker user ( I am asking the Actions team to see if there is anything we can do and maybe aligned the UIDs. What are you trying to do by the way? |
Thanks for the quick reply!
O, sorry about that, I did search a bit to see if there were any requirements like this but somehow I missed this.
👍
Was just using this action to do a build for PRs and then push it to a "staging" deployment. Been doing so with the FYI I worked around this by using setgid before running the action, that works fine. I've seen others work around it by running some |
Closing because I don't have a good workaround for that. Unfortunately this is in part how Actions and containers behave today. |
😢 |
Hi! First of all thanks for this repo/including GitHub Pages in Actions, it's nice to finally be able to see what's happening with a Pages build and deployment plus now we can use the exact same way GitHub Pages does a build or deployment in our own CI :)
One small thing I ran into is that the Docker image runs as root, so the files written by the build are also owned by root.
Since the GitHub runners run as UID 1001 GID 121 they are then unable to make any changes to these files.
I'm not sure if there's a policy within GitHub for these things, but it might make sense to use the same UID/GID as the runners? Also not running as root is a plus of course :)
The text was updated successfully, but these errors were encountered: