Re:Docker update ToS: Image retention limits imposed on free...
by qppo on Thursday August 13, 2020 @11:14AM
(#24144192)
You don't need to register an SSH key to download a public repo I thought
[ Parent
| on HN ]
Re:Docker update ToS: Image retention limits imposed on free...
by timdorr on Thursday August 13, 2020 @11:22AM
(#24144273)
Not an SSH key, but you do need an access token:
> You need an access token to publish, install, and delete packages in GitHub Packages.
https://docs.github.com/en/packages/using-github-packages-wi...
Re:Docker update ToS: Image retention limits imposed on free...
by qppo on Thursday August 13, 2020 @11:31AM
(#24144385)
...but not to download. You can clone a repo and download release artifacts without a PAT. That's only necessary for interacting with the API for actions that need authentication, which would be anything involving mutating a repository.
Re:Docker update ToS: Image retention limits imposed on free...
by timdorr on Thursday August 13, 2020 @01:06PM
(#24145579)
Yes, you need one to download. Note that you'll get an auth prompt for this Registry API URL:
https://docker.pkg.github.com/v2/test/test/test/tags/list
> "code": "UNAUTHORIZED", "message": "GitHub Docker Registry needs login"
Re:Docker update ToS: Image retention limits imposed on free...
by akerl_ on Thursday August 13, 2020 @12:52PM
(#24145426)
Using the GitHub Docker Registry requires auth, even just for downloads.
https://docs.github.com/en/packages/using-github-packages-wi...
GitHub Packages is different from GitHub Releases (and their artifacts) or cloning repos.
Re:Docker update ToS: Image retention limits imposed on free...
by mynameisvlad on Thursday August 13, 2020 @01:00PM
(#24145514)
> You need an access token to publish, install, and delete packages in GitHub Packages.
Yes, you do.
Re:Docker update ToS: Image retention limits imposed on free...
by laurencerowe on Thursday August 13, 2020 @01:36PM
(#24145913)
GitHub access tokens are a bit of a nightmare since you can't limit the permissions for a token. Only workaround I've found is to create another GitHub user for an access token and restrict that user's access.