-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Migrate to ghcr #16257
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
base: develop
Are you sure you want to change the base?
Migrate to ghcr #16257
Conversation
1d34e1d
to
cca21e5
Compare
# NOTE: Login to GHCR before running this script with a PAT: | ||
# echo $GHCR_TOKEN | docker login ghcr.io -u USERNAME --password-stdin | ||
# | ||
# Create a classic PAT with write:packages scope only visiting the following url: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I guess this is one of the things where the new PAT system isn't working?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is mentioned in their docs: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic
GitHub Packages only supports authentication using a personal access token (classic).
For more information, see [Managing your personal access tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
This PR migrates from dockerhub registry to ghcr.io. New images will be published to
ghcr.io/argotorg/solc
andghcr.io/argotorg/solidity-buildpack-deps
DOCKERHUB_TOKEN
should be removed from project secrets after merge.