apt-get update 404 on http://httpredir.debian.org/debian/dists/jessie/main/binary-amd64/Packages #31
Comments
|
It seems that there must've been a server down; it is working here. |
|
Weird, I get Not FoundThe requested URL /dists/jessie/updates/main/binary-amd64/Packages was not found on this server. Apache Server at security.debian.org Port 80 ''' Any ideas? |
|
I get the same |
|
Yeah, seems to work just fine here: $ docker run -it --rm debian:jessie apt-get update
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Ign http://httpredir.debian.org jessie InRelease
Get:2 http://security.debian.org jessie/updates/main amd64 Packages [182 kB]
Get:3 http://httpredir.debian.org jessie-updates InRelease [135 kB]
Get:4 http://httpredir.debian.org jessie Release.gpg [2373 B]
Get:5 http://httpredir.debian.org jessie-updates/main amd64 Packages [3653 B]
Get:6 http://httpredir.debian.org jessie Release [148 kB]
Get:7 http://httpredir.debian.org jessie/main amd64 Packages [9035 kB]
Fetched 9569 kB in 4s (2041 kB/s)
Reading package lists... Done |
|
Sounds like it's definitely a funky mirror hiccup. |
|
Must be something with my network setup then. Thank you all for trying. |
|
@bneijt - Maybe you fixed it, but I suspect your problem may have been like mine: I set up the proxy to whitelist HTH! :) |
|
I had another go and found my problem: it was a firewall setting. The hint that helped me was: HTTP did not work, FTP did work. The machine running the docker images also had a PREROUTING redirect rule for hosting on port 80 from an unprivileged program: This was causing HTTP to fail, but checks like ping to succeed. There was also a nice 404 because the local service on port 5000 was responding 404. Sorry for wasting time here! |
|
Actually it seems to still happen for me, without any firewall / web proxy: |
|
I am facing exact same issue |
|
For me it was docker-machine issue. It did not refresh DNS servers when I moved to another network. Restart of docker-machine has helped. |
|
Its a CDN issue I think, GET http://deb.debian.org/debian/dists/jessie/InRelease HTTP/1.1 responds with So HTTP/1.1 404 Not Found |
|
Have very similar issue on BananaPi single board computer today. SOLUTION: use aptitude instead of apt. |
|
I had the same problem. Here is the solution that helped me: https://robinwinslow.uk/2016/06/23/fix-docker-networking-dns/ |
|
apt-get update is failing :( W: Failed to fetch http://software.ligo.org/lscsoft/debian/dists/jessie/InRelease Unable to find expected entry 'contrib/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://ftp.de.debian.org/debian/dists/sid/InRelease Unable to find expected entry 'main/binary-sid/Packages' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-sid/Packages' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://ftp.us.debian.org/debian/dists/jessie/Release Unable to find expected entry 'main/binary-sid/Packages' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://ftp.de.debian.org/debian/dists/jessie/Release Unable to find expected entry 'main/binary-sid/Packages' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie/Release Unable to find expected entry 'main/binary-sid/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead |
|
Please try commenting the below line in /etc/apt/source.list deb [arch=amd64] https://download.docker.com/linux/debian xenial stable apt-get update works for me after commenting that line. |
|
If you are working behind a proxy you need to tell the docker the proxy settings. Use this alias to create a docker-build command with proxy settings: cat << EOF >> ~/.bashrc Then source the new bashrc: . ~/.bashrc Of course your proxy will be different. Ask your IT support. |
|
sudo service docker restart && docker build --no-cache=true . |
|
Thanks @Pherserk. I just restarted docker-machine and it worked. Already thought it's something really tough. |
|
I have the sane issue, but i don't have Docker... |
|
I had this issue, but it was fixed when I rebuilt the image with |
|
This is a python-acme issue : cerbot (free CA SSL certs). I just faced it tonight on debian strecth .. so same impact on Ubuntu platforms obviously .. does anybody already place a ticket about that (on debian or Ubuntu support platform) ? |
It seems that running
apt-get updatefails with404 Not Found. The referencedPackagesfile can be downloaded asPackages.gzandPackages.xzon the host, but not as plainPackages.Expected behavior: the newest version of the package index is downloaded
Actual behavior: 404 not found.
To reproduce:
The text was updated successfully, but these errors were encountered: