No symlinks but: Error: Artifact could not be deployed. Please ensure the content does not contain any hard links, symlinks and total size is less than 10GB.

[NickBorgers]

Select Topic Area

Question

Body

I can't figure out what I am doing to provoke failure of GitHub Pages deployment in an Action with the message:

Error: Artifact could not be deployed. Please ensure the content does not contain any hard links, symlinks and total size is less than 10GB.

Example run which gets this behavior.
As visible there the artifact was created successfully, is of appropriate size (1.3MB), and contains no symlinks.

I think I've followed the guidance published here for the deploy action.

• Creating artifact called github-pages
• Have appropriate permissions for the action
• Configured environment as recommended
• Have allowed the branch to deploy to github-pages

[ossanna16]

Hi there @NickBorgers and welcome to our community! Thank you for asking a great question 🙂
While you are waiting for a reply to your question, here are a few things you can do:

To get started, introduce yourself in our official introduction thread
To connect with other new users, check out this Discussion to Meet Your GitHub Community Team, further your GitHub knowledge by working through our GitHub Skill 🆙 exercises, and participate in our weekly Fun Friday chats

[vitalykarasik]

Weird - I don't see "upload artifacts" action in a log.
I suggest to do these things:

• bump GH Actions versions for 'checkout' and 'upload-artifacts'
• add 'ls -l .automated-rendering/screenshot-capture/screenshots/' debug step before artifact uploading

[NickBorgers]

The step right before the failed publish here is the upload-artifacts action. Its debug log includes listing of the files that get included in the tar file.

I can also see the files in the resulting artifact.

Regardless, switching to the pages-specific upload action fixed my problem.

[NickBorgers]

Switching to actions/upload-pages-artifact@v1 fixed my problem.

[danielkutik]

i had a file with permission set to chmod 600... deleting that file/changing the permission to 644 resolved the issue for me

[shivaramr]

Hey @danielkutik , where did you delete that chmod 600?

[danielkutik]

you could do chmod 755 path/to/problem/file or rm path/to/problem/file

[TheDevelolper]

Would be great to see an example of your deployment file because I'm not sure where I should put the script

[laraibg786]

Instead of using actions/upload-artifact, use actions/upload-pages-artifact when uploading artifacts for the pages deployment. This works with actions/deploy-pages@v4