Hint about permission settings for repository packages

[lufire]

For me, the initial GH Actions workflows failed due to the packages being set private by default in our organizations account (as far as i understand) and I had to link and set permissions in the package settings for the repository explicitly.
I think for people with no experience with this, as for me, it might cause trouble and a lot of time figuring out initially. Maybe additional hints in the README could help there. The second [!important] note is basically about this, however I could not directly see that "the distributed image" is equivalent to the package being pushed to "ghcr.io/.." and what is actually being talked about here without looking into the yaml files directly.
The current FAQ/Troubleshooting section is related, but only directly adresses the pulling step.

[hampusnasstrom]

@lufire thank you for the feedback! I will add a part to the troubleshooting section about checking the package permissions if the actions fail. Do you happen to remember the error message you got?

I'm not sure I understand the second part. Do you mean that it is not clear from the README that the repository creates two docker images and publishes these to GitHub's package registry?

[hampusnasstrom]

@lufire, I read through the README again and there is a line right at the top in the "Important" box saying:
"If you want to make the image public (recommended), you should make sure that your organization settings allow public packages and make this package public after building it. You can read more about this in the GitHub docs here." Is this not the first issue you mentioned?

[lufire]

@hampusnasstrom Maybe rephrasing that part would be enough? Right now it looks like it's optional and could be done afterwards, however it is crucial for the pipeline, otherwise you would need to include credentials in the workflow yamls, right?

[lufire]

@lufire thank you for the feedback! I will add a part to the troubleshooting section about checking the package permissions if the actions fail. Do you happen to remember the error message you got?

#27 ERROR: failed to push ghcr.io/zbt-tools/nomad-oasis:main: unexpected status from HEAD request to https://ghcr.io/v2/zbt-tools/nomad-oasis/blobs/sha256:5d8aab86fdb5cf7ccf1950ad75113fafc5d513c9a5efbbb0a1178344eebbcc1e: 403 Forbidden

I'm not sure I understand the second part. Do you mean that it is not clear from the README that the repository creates two docker images and publishes these to GitHub's package registry?

Yes :)

[hampusnasstrom]

@hampusnasstrom Maybe rephrasing that part would be enough? Right now it looks like it's optional and could be done afterwards, however it is crucial for the pipeline, otherwise you would need to include credentials in the workflow yamls, right?

I'm not sure actually. I thought I managed to publish a private package. But maybe you were trying to publish a public package when your organization rules did not allow this. Then I don't think even credentials will help.

[hampusnasstrom]

Thanks for the clarification, I'll try to make some changes and then tag you and you can let me know what you think.