I am so far able to use https://forgejo.org/docs/v1.19/user/packages/container/ in order to manually upload docker images to the OCI container registry connected to forgejo, but I am trying to integrate it into a forgejo workflow and am having trouble doing so:
What I want to do is use ${{secrets.FORGEJO_TOKEN}} instead of a token connected to an individual account.
What I tried:
- pass jibberish to
docker login with the project owner as the username -- login fails as expected
- pass the forgejo token to
docker login with the project owner as the username
- login passes
- but when I try to upload to the registry I get a
401 unauthorized response
Is there a way I can authorize the forgejo token to have write permissions to the packages?
### Comment
I am so far able to use https://forgejo.org/docs/v1.19/user/packages/container/ in order to manually upload docker images to the OCI container registry connected to forgejo, but I am trying to integrate it into a forgejo workflow and am having trouble doing so:
What I *want* to do is use ${{secrets.FORGEJO_TOKEN}} instead of a token connected to an individual account.
What I tried:
- pass jibberish to `docker login` with the project owner as the username -- login fails as expected
- pass the forgejo token to `docker login` with the project owner as the username
- login passes
- but when I try to upload to the registry I get a `401 unauthorized` response
Is there a way I can authorize the forgejo token to have write permissions to the packages?