It turns out that the problem with your build is that your repository name is only one character. (You discovered a bug in our validation on the create form) You shouldn’t have been able to create a repository with a one character name. They’ve made changes to the code base recently so that’s why you just started getting the errors.
Unfortunately you’re going to have to create a new repository for that build. When you name it just make sure it has at least two characters. (The site mentions 3 characters, but I just confirmed with the dev team that they have a PR that fixes the validation and will switch the 3 to 2)
We’ll do that, but is there any reason you’re blocking repos with single character names? We really like having kaggle/r, because the language R is just one character and fits nicely with the naming conventions we have with kaggle/python and kaggle/julia.
(As a side note, I noticed you’re in Indiana. There’s at least one more Docker user in Indiana - https://twitter.com/jeffmoser wrote most of the current version of kaggle.com & we’re big fans of Docker)
Edit:
When trying to push an image I get the following:
The push refers to a repository [mkroman/inspircd] (len: 1)
dc56c396d33b: Image push failed
FATA[0021] Error pushing to registry: Authentication is required.
I have te same error, With an automated build that was working fine for months, today i changed a little the Dockerfile and began to give this error "Error pushing to registry: Authentication is required."
I Delete and recreate the repo but no way
Is there any workaround???
@kizbitz I got this error now (June 26) .“Error pushing to registry: Authentication is required”.
Build id bfubsgfkjo8gwgjqcpassy5
Docker team: why do you keep replying that the issue is fixed, when it’s clearly not fixed, or comes right back all the time?
I ran into this, but in my case it’s because the repository had originally been setup as an automated build. Even without automated builds enabled, it would reject pushes. Deleting and recreating the repo fixed it.
