Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Issue with Docker 20.x - missing or empty Content-Type header #84

Open
piotr277 opened this issue Mar 18, 2021 · 3 comments
Open

Issue with Docker 20.x - missing or empty Content-Type header #84

piotr277 opened this issue Mar 18, 2021 · 3 comments

Comments

@piotr277
Copy link

Hello,
I'm facing serious issues when pulling images using Docker 20.x. (20.10 in my case)
The pull process is failing constantly with message:
Error response from daemon: missing or empty Content-Type header
I'm using proxy version 0.6.3.
This problem affects only pulling images from registry with basic authorization. It doesn't affect pulling from public repositories.
When I downgrade docker to 19.03 everything works fine! Some information about this workaround can be read here: goharbor/harbor#13740
@rpardini
Copy link
Owner

Hi, I did not get a chance to try 20.10 yet.
Is this on Mac?

@piotr277
Copy link
Author

I've no idea unfortunately. I'm using it on Ubuntu 20.04.

@huhouhua
Copy link

huhouhua commented Jul 26, 2024 •
edited
Loading

I also encountered this problem in version 25.0.0. I have two servers, one of which can respond normally, but the other cannot. I tried to use curl http://172.17.163.100:5000/v2/registry/manifests/2 and found that the server that could not respond had a missing response header.

[root@host1 (node) ~]$curl -v http://172.17.163.100:5000/v2/registry/manife
About to connect() to 172.17.163.100 port 5000 (#0)
Trying 172.17.163.100
Connected to 172.17.163.100 (172.17.163.100) port 5000 (#0)
GET /v2/registry/manifests/2 HTTP/1.1
User-Agent: curl/7.29.0
Host: 172.17.163.100:5000
Accept: */*
HTTP/1.1 200 ok
Server: Apache
Content-Length: 191
Cache-Control: no-cache
Connection: close

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312"
><title>Forbidden</title>
</head>
<body>
A ※U·AIÊOa,öløyE-CeA*eføy "ÜÀÍUE!
</body>
</html>
Closing connection 0

[songfuyu@iZ8vb0xdcv9l0nxpz0tcv6Z ~]$
curl -v http://172.17.163.100:5000/v2/registry/manifests/2
About to connect() to 172.17.163.100 port 5000 (#0)
Trying 172.17.163.100.
Connected to 172.17.163.100 (172.17.163.100) port 5000 (#0)
GET /v2/registry/manifests/2 HTTP/1.1
User-Agent: curl/7.29.0
Host: 172.17.163.100:5000
Accept: */*

HTTP/1.1 200 OK
Content-Length: 6858
Content-Type: application/vnd.docker.distribution.manifest.v1+prettyjws
Docker-Content-Digest: sha256:5ce9ba3e373eddf7eba72760a59737cde30dcd7875df31146f4beec96791c2633
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:5ce9ba3e373eddf7eba72760a5937cde30dcd78375df31146f4beec96791c2633"
X-Content-Type-Options: nosniff
Date: Fri, 26 Jul 2024 12:41:55 GMT
{
"schemaVersion": 1,
"name": "registry",
"tag"
"architecture": "amd64",
"fsLayers": [
"blobSum": "sha256:a3ed95caeb02ffe68cdd9fd844096680ae93d633cb16422d00e8a7c22955b46d4
"blobSum": "sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"
"blobSum": "sha256:a37b1bf6a96f6fcb5ac2b9a981,a0648dbe58720ef98db756a79dbed55488d211"
.....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rpardini @piotr277 @huhouhua