Update see solution. Environments and logins getting in the way.
I’ve published some general use containers in my OSS Ultimate group.
Following what I understand to be the behavior documented here: Container registry visibility permissions, I expected a simple docker pull to “just work” (see below image). Instead, from an different machine, I get the following:
% docker pull registry.gitlab.com/another15y/mavenpg:3.9.8-eclipse-temurin-21
...
Error response from daemon: Head
"https://registry.gitlab.com/v2/another15y/mavenpg/manifests/3.9.8-eclipse-temurin-21":
unauthorized: HTTP Basic: Access denied. The provided password or token is incorrect or your account
has 2FA enabled and you must use a personal access token instead of a password. See
https://gitlab.com/help/user/profile/account/two_factor_authentication#troubleshooting
I’m not ignoring the message, clearly I have some setup that is intentional and the message is telling me something important. However, as noted above, my configuration for the container registry follows the expectation shown below:
I’ve found some possibly related questions as well, but this seems to more about internal use cases in CI, Pulling Docker image from GitLab Container Registry stopped working, only for one project.
Any thoughts on where my expectations are going wrong?