May 16, 201610 yr Update. DNS messed up by PiHole (I think). Set DNS in unRaid network settings, everythings all good now. Running unRaid 6.2.0-beta21 I can install dockers from a number of different repositories. They seem to take a little while but that isn't the problem. Any dockers from linuxserver.io refuse to pull, I have a notion from some comments around the internet that it could be due to an incorrect MTU value. Can anyone direct me to a solution? My Google-fu has failed me. Install log below. Pulling image: linuxserver/couchpotato:latest IMAGE ID [98aae5d8e559]: Pulling image (latest) from docker.io/linuxserver/couchpotato. Pulling image (latest) from docker.io/linuxserver/couchpotato, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [f7eef3e8d2a5]: Pulling metadata. TOTAL DATA PULLED: 0 B docker: Error response from daemon: Get https://registry-1.docker.io/v2/linuxserver/couchpotato/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alinuxserver%2Fcouchpotato%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See '/usr/bin/docker run --help'. Many Thanks.
May 28, 201610 yr Same problem here (unRaid v6.1.9), however setting the DNS in unRaid network settings didn't help. The unRaid server can download and update apps, so has access to the internet. Pulling image: linuxserver/mariadb:latest IMAGE ID [74de922b9e36]: Pulling image (latest) from linuxserver/mariadb. Pulling image (latest) from linuxserver/mariadb, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [f7eef3e8d2a5]: Pulling metadata. Error pulling dependent layers. IMAGE ID [74de922b9e36]: Error pulling image (latest) from linuxserver/mariadb, endpoint: https://registry-1.docker.io/v1/, HTTP code 400. Error pulling image (latest) from linuxserver/mariadb, HTTP code 400. TOTAL DATA PULLED: 0 B
May 30, 201610 yr Author I think your issue might be different to mine. I don't think mine was pulling any data because the install was never managing to get addresses from the DNS thus the timeout. Where as a HTTP code 400 is according to w3.org, HTTP Code 400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. I guess yours is only happening for linuxserver dockers like mine though? Maybe head to their forums and ask around?
May 30, 201610 yr Thanks for digging for the HTTP code 400 meaning. I was too lazy , assuming something wrong on my side (Newbie, 1st docker). anyway "malformed syntax" might suggest otherwise. I will ask is linuxserver's MariaDB thread or linuxserver forums. Edit: The problem is on my server. A different docker, same result: Pulling image: gfjardim/crashplan:latest IMAGE ID [aee938d09f63]: Pulling image (latest) from gfjardim/crashplan. Pulling image (latest) from gfjardim/crashplan, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [f7eef3e8d2a5]: Pulling metadata. Error pulling dependent layers. IMAGE ID [aee938d09f63]: Error pulling image (latest) from gfjardim/crashplan, endpoint: https://registry-1.docker.io/v1/, HTTP code 400. Error pulling image (latest) from gfjardim/crashplan, HTTP code 400. TOTAL DATA PULLED: 0 B Edit2: Installed other dockers successfully. Seems a Docker Hub problem, however it's odd that others don't have it or have a way to solve it.
Archived
This topic is now archived and is closed to further replies.