-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tart Push to GitLab Registry Failing #914
Comments
How do you authenticate with the registry? |
I authenticate with the registry using GitLab CI's token. The specific login command I use is:
I discovered that commenting out the following line in the tart project's source allowed me to successfully push to the gitlab registry:
This workaround resolved the issue I was experiencing. However, I haven't yet identified the specific cause of this issue. |
I've managed to successfully push a cloned Could you please try pushing the same image to your GitLab server using your own credentials (and not a temporary CI ones)? |
Hi, I'm getting the same error as @yangyi625:
Using Tart The push is done by using a Personal Access Token still valid for a couple of months. After retrying the command several tries the upload percentage does increase. |
Downgrading to Tart version To downgrade: curl -O https://raw.githubusercontent.com/cirruslabs/homebrew-cli/b516c00303c4ad55f636ac3fdd689dd04ff5e46e/tart.rb
brew install --build-from-source tart.rb |
Hi @edigaryev , Using a personal token works fine, but I still prefer to use a CI token. I tried using Mitmproxy to see which part was causing the error. The results are as follows: It looks more like it's getting a 401 error during upload. The response is as follows: I can't quite understand why I'm encountering an authentication issue here |
try to use --concurrent 1. For us the same issue appeared and got fixed by the concurrent 1. Also I tried adding a "retry" for the blobtransmission and it also helped with pulling and pushing images. Maybe I should contribute. |
System Information
Problem Description
The text was updated successfully, but these errors were encountered: