CODEWITHSUNDEEP
azure-pipelines-build-taskazure-container-registry
fhilton
fhilton

Reputation: 748

VSTS push to Azure Container Registry - getting timouts or "V1 endpoint is not supported"

Created a Docker Build Task in VSTS to push to Azure Container Registry.

Worked fine yesterday, today I'm getting either an error or a timeout with each retry.

I tried adding a new Registry and build task but getting the same errors.

Error 1 - "V1 endpoint is not supported":
enter image description here

Error 2 - Timeout:
Some parts of the image push, others timeout until it fails.
enter image description here

Azure Support asked me to post here.

Upvotes: 1

Views: 926

Answers (2)

Yu Wang
Yu Wang

Reputation: 71

TSL timeout could be due to network connection issues.

The "V1 endpoint is not supported" error stems from the docker client behavior. Basically docker client will first try to connect to the registry server on V2 endpoint (/v2/); if it can't connection or connection times out, it will try to connect the registry on V1 endpoint (/v1/), in case the registry is an old v1 registry. Azure Container Registry only supports V2 endpoint so if there is request targeting for V1 endpoint, it returns such error message.

Both somehow seemed due to slow connection on TLS. If you see the error consistently, you can contact Azure Container Registry team or Microsoft support team with your subscription information, registry name and time frame of the issue so the team can help to investigate further.

Upvotes: 1

Jitendra
Jitendra

Reputation: 782

TSL timeout is due to slow network connectivity. You can overcome this by decreasing the number of images concurrently getting uploaded in docker daemon. Use --max-concurrent-uploads with dockerd and set the max concurrent upload to 1 and you may also decrease the concurrent download. Help: https://docs.docker.com/engine/reference/commandline/dockerd/#options.

For “V1 endpoint is not supported” error, are you using hosted or private pool. If its private pool can you check the docker client installed on the agent where you are getting this error. I have a hunch that it might have an old version of docker client installed on it.”

Upvotes: 0

Related Questions