moby: Unable to get docker updates for Ubuntu 14.04 LTS Trusty Tahr
I was trying to update(apt-get update) my system an the following errors were notified
Err https://apt.dockerproject.org ubuntu-trusty/main amd64 Packages
Received HTTP code 403 from proxy after CONNECT
Err https://apt.dockerproject.org ubuntu-trusty/main i386 Packages
Received HTTP code 403 from proxy after CONNECT
.
.
.
W: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-trusty/main/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT
W: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-trusty/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT
E: Some index files failed to download. They have been ignored, or old ones used instead.
Below is my OS version and docker details
Docker Version : Docker version 1.8.2, build 0a8c2e3
Docker info :
Containers: 25
Images: 12
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 62
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-65-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 8
Total Memory: 7.687 GiB
Name: workspace
ID: AL47:NZ7R:F2LN:7SZQ:U7BQ:2E5C:P4MS:ZWG6:T5H6:NY5Z:ATD2:JIT3
WARNING: No swap limit support
uname -a : Linux workspace 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
The website I followed to install docker : https://docs.docker.com/installation/ubuntulinux/
Why does this happen? Can this issue affect other programs that use docker ?
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 73 (26 by maintainers)
Use http instead of https in /etc/apt/sources.list.d/docker.list. It helped me.
Hello Guys, has this issue resurfaced today? Fix onda way?
I’m testing on a fresh ubuntu VM
ubuntu/trusty64
(usingvagrant
).Failures:
A quick status update since my last comment; the infra team is now working on this issue as well, and is currently in contact with AWS. So far it looks like the issue is not on our side, but I’ll post more information when it becomes available
changing http to https in the sources.list.d/docker.list fixed the issue
changing to http worked for me.
Just got informed that AWS identified a possible cause and is rolling out updates. It may take some time for those to be available everywhere. Hopefully the issue will be resolved by that.
https -> http helps, but man in the middle is happy now
I also run into the issue while updating the repos:
This was because the source was defined in multiple files:
I removed
/etc/apt/sources.list.d/docker.list.save
,/etc/apt/sources.list.d/docker.list
and removed the docker entry from/etc/apt/sources.list
.Next I followed the instructions from the Dockers install documentation:
After the steps above I got a clean
apt-get update
.We’re currently having an issue with the APT repository (see https://github.com/docker/docker/issues/23203). I raised this issue internally, and we’re trying to get this fixed ASAP
As a temporary workaround, you can install docker 1.11.2-rc1 from the “test” repository; 1.11.2-rc1 is almost the same as the current release, apart from these three changes; https://github.com/docker/docker/pull/23164, https://github.com/docker/docker/pull/23169, and https://github.com/docker/docker/pull/23176
Those changes should not make a functional difference (and the last change only affects some corner-cases)
You can install the RC, either by changing the “main” to “test” repository for APT, or using the install script;
Remember to switch back to the regular (main) repository after the issue is resolved
Did not helped 😦
@petewilcock @fperret if you followed the manual instructions on https://docs.docker.com/engine/installation/linux/ubuntu/ today, it could be a different issue; there’s an error in the installation instructions, and because of that, an incorrect path is used to get the packages.
There’s a number of pull requests open to fix this, and will be addressed later today; you can find the correct instructions in this PR; https://github.com/docker/docker.github.io/pull/1243/files
I have been seeing this again today also, the work-arounds above (hardcoded ip for apt host, https/http) only get so far and am blocked at
GPG error: https://apt.dockerproject.org ubuntu-trusty InRelease: The following signatures couldn't be verified because the public key is not available
and am prompted that docker-engine is unauthenticated and am reluctant to force.
changed from https => http works for me too.
btw, for all those having a problem, if I use
http://apt.dockerproject.org/repo ubuntu-trusty main
(noHTTPS
) it works.@RickMohr
debian-trusty
is not a proper distribution name.It should be
ubuntu-trusty
if you’re on ubuntu or one of the debian variant otherwise (e.g.debian-stretch
,debian-jessie
)Update your
/etc/apt/source.lilst.d/docker
accordingly.the problem seems to be fixed
Just to let you know: My Linux-based Travis builds are now failing:
changing to http worked for me too.