-
Notifications
You must be signed in to change notification settings - Fork 79
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
Deployment fails if files are not writable or owned by root #58
Comments
ℹ️ While it's not a complete fix, as this should indeed be handled on the server-side eventually, we have added a partial fix to the Since you are using that Action with Please let us know if you're still running into issues. |
The permission problem itself might be resolved but in the example of OP, the directory for deployment is a symlink itself where the contents of Probably because chmod is running in |
@sempruijs looks like this is the issue you've been encountering |
We made changes recently around that which should help. Closing. |
@yoannchaudet are those changes merged/released yet? I ran into the same issue, with nix, too. |
The permissions fix is included in https://github.com/actions/upload-pages-artifact/releases/tag/v1.0.6. It's best effort and we don't change ownership on the files. If that's your issue, I am afraid you will need to handle that yourself with an extra |
Why is it not possible to take care of necessary ownership requirements with this action? I am glad to help out. |
Running into this aswell. Is the chown still the way to use this? |
actions/deploy-pages#58 has more details.
Hi there,
I tried to deploy my site which is built with NIx and
actions/deploy-pages
would fail with a cryptic error message.Which outputs this:
From my testing
actions/deploy-pages
fails if the files are either not writable or owned by root. The output of a Nix build is both not writable and owned by root. I worked around this by clearing the permissions after building:I don't think this should fail, since I expect the file permissions be cleared on deployment. Even so, the error message should at least be more clear.
The text was updated successfully, but these errors were encountered: