Why Docker Will Sometimes Fail and Produce 400-Series Errors

Why Docker Will Sometimes Fail and Produce 400-Series Errors

AuthorFullName__c
Sankar Kumar D
articleNumber
000001458
ft:sourceType
Salesforce
FirstPublishedDate
2016-10-06T13:38:24Z
lastModifiedDate
2024-03-10T07:46:24Z
VersionNumber
5

If your Docker client occasionally fails with 400 errors, it is likely due to a timeout issue with the reverse proxy. Different reverse proxies will often have different settings that control timeouts. Regardless of where those settings are to be found, your solution to this problem will typically be to increase the timeout period. As the two most common reverse proxies in use with Artifactory are Nginx and Apache, here are configurations that may help you: 

NGINX

 proxy_read_timeout 900; # Typically applied to the Artifactory/Docker server block

 send_timeout 300; # Typically applied to the http server block

Apache

TimeOut 300

After you have made your changes to your configuration file, be sure to restart your reverse proxy before attempting the Docker operation again.

Docker Error

Although the exact error will vary based on the Docker version you’re using, you can expect
to see something like this:

Error: Status 400 trying to pull repository mbajor/ansible: "{n "errors" : [ {n "status" : 400,n "message" : "Unsupported docker v1 repository request for 'docker-local'"n } ]n}"