Install mkdocs-material-insiders with docker leads to an insufficient_scope error

[robingenz]

Description

I am trying to install mkdocs-material-insiders with Docker as described here.
I followed the steps exactly and after creating the GitHub release I get the following error message in the GitHub Actions workflow in the Publish Docker image step:

...
#37 exporting attestation manifest sha256:be81eefd5c44acc495e20f19a82a05d30f229cf128b02c673ddc9c9296cd487b 0.0s done
#37 ...

#38 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#38 DONE 0.0s

#37 exporting to image
#37 exporting manifest list sha256:db83a971881c921604296ee13b74c81098ae2c3667e1a1af0a379b1717d49ad3 done
#37 pushing layers
#37 ...

#39 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#39 DONE 0.0s

#40 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#40 DONE 0.0s

#41 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#41 DONE 0.0s

#42 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#42 DONE 0.0s

#37 exporting to image
#37 pushing layers 0.3s done
#37 ERROR: failed to push robingenz/mkdocs-material-insiders:9.1.1-insiders-4.32.2: server message: insufficient_scope: authorization failed
------
 > exporting to image:
------
ERROR: failed to solve: failed to push robingenz/mkdocs-material-insiders:9.1.1-insiders-4.32.2: server message: insufficient_scope: authorization failed
Error: buildx failed with: ERROR: failed to solve: failed to push robingenz/mkdocs-material-insiders:9.1.1-insiders-4.32.2: server message: insufficient_scope: authorization failed

Related links

• Installation with docker

Proposed change

No response

Before submitting

• I have read and followed the documentation issue reporting guidelines.
• I have attached the links to the described sections of the documentation

[squidfunk]

Thanks for reporting. The error message is actually pretty clear – the access token has insufficient scopes. More specifically, the write:packages scope seems to be missing. Please note that you need to use a specific token, called GHCR_TOKEN – just in case you missed it. Additionally, please make sure that you really followed the steps outlined in the documentation, because this is what we all use successfully to build the Docker image. Specifically:

• Create a new personal access token (why?)
  • Go to https://github.com/settings/tokens
  • Click on Generate a new token
  • Enter a name and select the write:packages scope
  • Generate the token and store it in a safe place
• Add a GitHub Actions secret on your fork
  • Set the name to GHCR_TOKEN
  • Set the value to the personal access token created in the previous step

Converting to discussion, since this I'm confident that this is not an issue with our documentation.

[squidfunk]

All this is in case you use the Docker build and release workflow provided by us, which uses the GitHub Container Registry. Note that if you use another registry like DockerHub, you're more or less on your own and might need to adjust those settings.

Thus, we recommend just using GHCR.

[robingenz]

Thank you for your fast response!

More specifically, the write:packages scope seems to be missing.

This is already set:

Please note that you need to use a specific token, called GHCR_TOKEN – just in case you missed it.

I also did that:

It seems to be trying to push the image to DockerHub or logging into DockerHub instead of GitHub Packages because of this log entry:

...
#42 [auth] robingenz/mkdocs-material-insiders:pull,push token for registry-1.docker.io
#42 DONE 0.0s
...

Could this possibly be the problem? However, I have not changed anything in the workflow. It is the same as in the fork.

[squidfunk]

Please try to sync the Insiders repository, we recently fixed an issue with the build script.
https://github.com/squidfunk/mkdocs-material-insiders/commit/68510cb1cedff4c15b09939a308bb84437c3da27

[robingenz]

Great, that works. My mistake was to use the latest release and not test the current master version. Thanks for your help!

[squidfunk]

My fault to not release it immediately. Just released 4.23.3 with the latest workflow.