Summary
Manually pushing a large docker container (2.06GB) from my machine to a private repository fails after a few minutes with the following error:
unauthorized: authentication required
However, pushing a smaller docker container (920MB) (the official python image from docker) to the same private repository succeeds. Note that previously I have been able to push a larger version of this exact same image in the past. So I am not sure what has changed in Gitlab SAAS since then that is now causing this issue.
contains the token you just created. You should receive feedback that it was successful and can even inspect that it was added to your credentials manager (I am using
). Note you may want to update the
as it warns that passing the token on the command line is not safe and you should instead use the way I have described that is in the docker documentation.
Example Project
Not sure how difficult this is to do. I have a few ideas. Let me know if you absolutely need this. Looking back at some issues in the past I see this problem has popped up a few times before.
What is the current
bug
behavior?
The small images is pushed to the container registry successfully but the large image fails with the authentication error described.
Either the large image should be pushed to the container registry with the current configuration. Or if that is not possible, then there should be access to be able to extend the default token expiration above 5 minutes for the registry when using Gitlab.com. I presume that the Admin area > Settings > CI/CD > Container Registry > Authorization token duration (minutes) only exists on self-managed Gitlab instances and not on Gitlab SAAS because I do not see it anywhere.
Output of checks
This bug happens on GitLab.com.
