search

docker / for-linux

Docker Engine for Linux
https://docs.docker.com/engine/installation/
756 stars 85 forks source link

debian repository: The HTTP server sent an invalid reply header #803

Open ZiTAL opened 5 years ago

ZiTAL commented 5 years ago

Expected behavior

update the repo information

Actual behavior

Ign:6 https://download.docker.com/linux/debian stretch InRelease         
Err:7 https://download.docker.com/linux/debian stretch Release                                      
  The HTTP server sent an invalid reply header
E: The repository 'https://download.docker.com/linux/debian stretch Release' does not have a Release file.

Steps to reproduce the behavior

I have this repo in apt:

deb [arch=amd64] https://download.docker.com/linux/debian stretch stable

and get error updating repos with:

apt-get clean
apt-get update
havesomepham commented 3 years ago

I'm also having this same issue running sudo apt-get update where it just gives me a The HTTP server sent an invalid reply header error. Did you find a solution?

aqueos commented 3 years ago

the easiest way is to replace temporarily uname by a little script that return fix data for the -r

like : mv /bin/uname /bin/uname.orig nano /bin/uname

!/bin/bash

if [[ $1 == "-r" ]] ;then echo '4.9.250-vs2.3.9.12aq'; exit else uname.orig $1 fi

ZiTAL commented 3 years ago

@aqueos Where do you find what code use to fake the uname?

aqueos commented 3 years ago

@aqueos Where do you find what code use to fake the uname?

i am sorry i should have put more context here, i dont remember why i posted this one here so i hope i did not put this in the wrong ticket. I encountered the issue solved by the wrapper trying to upgrade while being on a kernel with revision > 255. with the libc having a limit to 255 has a kernel version, so any kernel version reported with a revision number under 255 make the package happy.

not sure it belongs here, sorry if if missposted on the wrong ticket by messing up browsers tabulations :(

regards.

ZiTAL commented 3 years ago

@aqueos I don't try your solution but I have a 4.9.0-0.bpo.8-amd64 kernel, maybe the apt version is old and is not compatible with this kind of repositories. With another repository of other software occurs the same :(

aqueos commented 3 years ago

its probably an error on my part, sorry for this.

thaJeztah commented 3 years ago

Note that debian 9 "stretch" reached EOL, and we no longer publish packages for this version of Debian; https://www.debian.org/releases/stretch/

Debian 9 has been superseded by Debian 10 (buster). Security updates have been discontinued as of July 6th, 2020.

(that page mentions Debian 10 "buster", which by now also has reached EOL), so if you're running Debian 9 or 10, I'd highly recommend updating to the current (11) release of Debian, and to be sure that the package repository you have configured for docker matches your distro version.

thaJeztah commented 3 years ago

I'm not sure if there's anything actionable here (I for sure know there's many people installing the debian packages, so at least it's not a generic issue)