Docker Community Forums

Share and learn in the Docker community.

Error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found\n"


(Glassboxdigital) #1

Hey
since this morning we have an issue to push to images to Docker-hub
we getting this error

1. "error parsing HTTP 404 response body: invalid character ‘p’ after top-level value: "404 page not found\n"
2. "unknown blob"

please find the information below

1. error parsing HTTP 404 response body: invalid character ‘p’ after top-level value: “404 page not found\n” 18:15:48 Build step ‘Execute shell’ marked build as failure

2. we getting error “unknown blob” right after the docker push process is going to ended !

11:43:54 5a76f6a09a69: Pushed
11:43:55 ec9df5f1a2bd: Pushed
11:43:55 88856b11b50f: Pushed
11:43:55 7ce48c206d82: Layer already exists
11:43:55 a40eb036725c: Layer already exists
11:43:56 d7d48188b655: Layer already exists
11:43:56 b176545a110b: Layer already exists
11:43:57 cc788d7feedb: Layer already exists
11:43:57 f75e64f96dbc: Layer already exists
11:43:57 8f7ee6d76fd9: Layer already exists
11:43:58 c23711a84ad4: Layer already exists
11:43:58 90d1009ce6fe: Layer already exists
11:43:59 1d0d249d60a5: Pushed
:4**3:59 unknown blob
11:43:59 Build step ‘Execute shell’ marked build as failure

Steps to reproduce the behavior

Output of docker version :

Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a215d7133c34aa18e3b72b4a21fd0c6136
 Built:             Fri Oct 26 23:38:29 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a/18.06.1-ce
  Built:            Fri Oct 26 23:39:57 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Output of docker info :

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 61
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.14.77-81.59.amzn2.x86_64
Operating System: Amazon Linux 2
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.42GiB
Name: qa-dockerslave
ID: 6TPO:3M25:PT3E:V2DG:4VU2:IUE2:OALV:O7XI:PI2R:JG4Y:LDTC:WSGR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.)
We are running Docker inside AWS

please advise for your help

Thanks
please help if someone as the same issue


(Glassboxdigital) #2

Any Update ?
This issue is critical

Please advise

Thanks


(Robgiffin) #3

I’m seeing this too - namely error #1 - error parsing http 404 response. This is happening from our docker servers in AWS and when trying to build images in AWS codebuild. It seems to have started like on friday. Docker - don’t you have a status page for your services??


(Northtyphoon) #4

Docker Hub Status Page: https://status.docker.com/pages/533c6539221ae15e3f000031


(Glassboxdigital) #5

Hey Docker…
Can You please be more specific about this issue? do u need more information to monitor or analysis this open issue ? , i
t’s so critical that most of the people can’t upload they version since last Friday , can we have more attention than to share with us the status page…?
please find below log from the "journalctl -fu docker.service"
Nov 25 19:50:57 dockerd[15832]: time=“2018-11-25T19:50:57.822340283Z” level=warning msg="failed to upload schema2 manifest: error parsing HTTP 404 response body: invalid character ‘p’ after top-level value: “404 page not found\n” - falling back to schema1"
Nov 25 19:51:33 dockerd[15832]: time=“2018-11-25T19:51:33.948707259Z” level=error msg="Upload failed: unknown blob"
Nov 25 19:51:33 dockerd[15832]: time=“2018-11-25T19:51:33.948807363Z” level=info msg="Attempting next endpoint for push after error: unknown blob"

Thanks


(Glassboxdigital) #6

Thanks Rob
I’m agree with you, i opened another bug status on GitHub and i see more & more people suffering
how you dealing with this open issue so far ? any suggesting

Thanks for your response …


(Glassboxdigital) #7

Hey,
I can confirm, the issue was resolved, we can upload our docker images
Thanks Docker for the quick respond …:slight_smile:
You can go a head and close the this issue

Thanks again
.Yossi


(Kritesh89) #8

If you persist n 404 error and your page not responding then its main reason is your client not giving response so you need to interact your that page with your website and solve it with the help of Redirection. You can use 301 Redirection this will resolve your issue.


(Kritesh89) #9

Thanks for your response this will helps to resolve this issue. If you resolve your server issue then 404 error will remove easily.