Pushing package from workflow *sometimes* fails with "User cannot be authenticated with the token provided."

[psalz]

Select Topic Area

Question

Body

I'm seeing some confusing behavior when trying to push container images from a workflow to the GitHub container registry, where pushing fails sometimes with error unauthorized: unauthenticated: User cannot be authenticated with the token provided., but then may work again if I re-run the failed jobs.

Take a look at this run:

• As you can see, in attempt #3, two out of seven containers (celerity-build/dpcpp:ubuntu22.04-HEAD and celerity-build/dpcpp:ubuntu20.04-61e51015) failed to push to the registry with the error unauthorized: unauthenticated: User cannot be authenticated with the token provided.
• If you go to attempt #2 you will see that previously also celerity-build/dpcpp:ubuntu22.04-62ecb849 failed to push. These are the same packages, only different tags!
• Finally, in attempt #1, two pushes for the other package (celerity-build/hipsycl:ubuntu22.04-d2bd9fc7 and celerity-build/hipsycl:ubuntu20.04-d2bd9fc7) also failed with the same error.

All packages are public and I did not change any settings between workflow run attempts.

[psalz]

We solved it: The problem is that logging into Docker is stateful, and we were running multiple jobs concurrently on the same machine using self-hosted runners. Moving the call to docker login right before docker push seems to work well enough for now (although there's still a race, of course).