Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
apt repo for Xenial says the package cannot be authenticated #22599
Comments
|
did you run |
hamid-elaosta
commented
May 9, 2016
•
Edited 1 time
-
hamid-elaosta
May 9, 2016
-
May 9, 2016
|
@thaJeztah Yes, indeed. And the key in case anyone is wondering (showing it's already installed): |
|
I don't have a physical box to test on, but I just created a fresh Ubuntu Xenial droplet on DigitalOcean, but I'm not able to reproduce, using these steps; apt-get update
apt-get install apt-transport-https ca-certificates
apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
echo "deb https://apt.dockerproject.org/repo ubuntu-xenial main" > /etc/apt/sources.list.d/docker.list
apt-get update
apt-get install docker-engine |
|
(skipped some steps, such as installing dependencies for aufs, and updating apparmor) |
hamid-elaosta
commented
May 9, 2016
|
Ok, I solved it by deleting the key from the documentation: HERE Unfortunately, this means, since I did not receive the pubkey directly from the Docker documentation I have no way to prove the docker-engine I downloaded is the version from Docker themselves, that it is genuine, or even that the signature I retrieved from the keyserver is really whom it claims to be. Essentially, for all intents and purposes, I have circumvented the exact reason package signatures exist, which is to prove the author. and instead using the one suggested in the out put of apt-get update |
|
your output states; What does |
|
Never mind, I suspect that's the output of the GPG error only. But don't understand why it wouldn't work for you |
|
ping @tianon any ideas what can cause this? I'm not able to reproduce |
hamid-elaosta
commented
May 9, 2016
|
@thaJeztah That did make me wonder, when I saw that, but here's the content: |
|
Sorry, I don't have a clear answer what can cause this. Is there something special in your setup (a proxy-server, |
hamid-elaosta
commented
May 9, 2016
|
Not that I'm aware of, but it's possible something operations have done I'm unaware of. I've set up all the systems now by deleting the keys and adding the one suggested in apt-get update. I'll look into it more if it occurs again. Thanks. |
mrmikee
commented
May 10, 2016
•
Edited 1 time
-
mrmikee
May 10, 2016
-
May 10, 2016
|
I was able to reach all Ubuntu official ppa's, but I had the problem of not getting the keys for the Docker ppa. Which is what led me to this post. added proxy settings. Seems the company proxy allowed direct to "official" ppa's but proxied the one for docker. This 'fixed' the key issue but there still remains the issue of verification. Still have issue verifying package: |
|
I have this problem too. I am using this: I'm using this with I've logged in to the box and tried to add tried this: As you can see, there is clearly an issue with signing. |
added a commit
to kubernetes/kubernetes-anywhere
that referenced
this issue
May 11, 2016
|
I can't reproduce: FROM ubuntu:xenial
RUN apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 \
--recv-keys 58118E89F3A912897C070ADBF76221572C52609D
RUN echo 'deb http://apt.dockerproject.org/repo ubuntu-xenial main' \
> /etc/apt/sources.list.d/docker.list
RUN apt-get update && apt-get install -y docker-engine
RUN docker -v(output below trimmed for readability) $ docker build .
Sending build context to Docker daemon 2.048 kB
Step 1 : FROM ubuntu:xenial
---> c5f1cf30c96b
Step 2 : RUN apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
---> Running in a8f553d5d9bb
Executing: /tmp/tmp.CB21FieIfD/gpg.1.sh --keyserver
hkp://p80.pool.sks-keyservers.net:80
--recv-keys
58118E89F3A912897C070ADBF76221572C52609D
gpg: requesting key 2C52609D from hkp server p80.pool.sks-keyservers.net
gpg: key 2C52609D: public key "Docker Release Tool (releasedocker) <docker@docker.com>" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
---> 0badecc43513
Removing intermediate container a8f553d5d9bb
Step 3 : RUN echo 'deb http://apt.dockerproject.org/repo ubuntu-xenial main' > /etc/apt/sources.list.d/docker.list
---> Running in 4bd4bf38861b
---> 304769780460
Removing intermediate container 4bd4bf38861b
Step 4 : RUN apt-get update && apt-get install -y docker-engine
---> Running in 11363734857d
Ign:1 http://apt.dockerproject.org/repo ubuntu-xenial InRelease
Get:2 http://apt.dockerproject.org/repo ubuntu-xenial Release [19.7 kB]
Get:3 http://apt.dockerproject.org/repo ubuntu-xenial Release.gpg [801 B]
Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:5 http://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages [1224 B]
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
...
Get:25 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [6767 B]
Fetched 23.0 MB in 2s (8896 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
The following additional packages will be installed:
apparmor aufs-tools busybox-initramfs ca-certificates cgroupfs-mount cpio
dh-python file git git-man ifupdown initramfs-tools initramfs-tools-bin
initramfs-tools-core iproute2 iptables isc-dhcp-client isc-dhcp-common
klibc-utils kmod krb5-locales less libapparmor-perl libasn1-8-heimdal
libatm1 libbsd0 libcurl3-gnutls libdns-export162 libedit2 liberror-perl
libexpat1 libffi6 libgdbm3 libgmp10 libgnutls30 libgssapi-krb5-2
libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal
libheimntlm0-heimdal libhogweed4 libhx509-5-heimdal libidn11
libisc-export160 libk5crypto3 libkeyutils1 libklibc libkrb5-26-heimdal
libkrb5-3 libkrb5support0 libldap-2.4-2 libltdl7 libmagic1 libmnl0 libmpdec2
libnettle6 libnfnetlink0 libp11-kit0 libperl5.22 libpopt0 libpython3-stdlib
libpython3.5-minimal libpython3.5-stdlib libroken18-heimdal librtmp1
libsasl2-2 libsasl2-modules libsasl2-modules-db libsqlite3-0 libssl1.0.0
libtasn1-6 libwind0-heimdal libx11-6 libx11-data libxau6 libxcb1 libxdmcp6
libxext6 libxmuu1 libxtables11 linux-base mime-support netbase
openssh-client openssl patch perl perl-modules-5.22 python3 python3-minimal
python3.5 python3.5-minimal rename rsync udev xauth xz-utils
Suggested packages:
apparmor-profiles apparmor-profiles-extra apparmor-docs apparmor-utils
mountall libarchive1 libdpkg-perl gettext-base git-daemon-run
| git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch
git-cvs git-mediawiki git-svn ppp rdnssd bash-completion iproute2-doc
resolvconf avahi-autoipd isc-dhcp-client-ddns gnutls-bin krb5-doc krb5-user
libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql
libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal ssh-askpass
libpam-ssh keychain monkeysphere ed diffutils-doc perl-doc
libterm-readline-gnu-perl | libterm-readline-perl-perl make python3-doc
python3-tk python3-venv python3.5-venv python3.5-doc binutils binfmt-support
openssh-server
The following NEW packages will be installed:
apparmor aufs-tools busybox-initramfs ca-certificates cgroupfs-mount cpio
dh-python docker-engine file git git-man ifupdown initramfs-tools
initramfs-tools-bin initramfs-tools-core iproute2 iptables isc-dhcp-client
isc-dhcp-common klibc-utils kmod krb5-locales less libapparmor-perl
libasn1-8-heimdal libatm1 libbsd0 libcurl3-gnutls libdns-export162 libedit2
liberror-perl libexpat1 libffi6 libgdbm3 libgmp10 libgnutls30
libgssapi-krb5-2 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal
libheimntlm0-heimdal libhogweed4 libhx509-5-heimdal libidn11
libisc-export160 libk5crypto3 libkeyutils1 libklibc libkrb5-26-heimdal
libkrb5-3 libkrb5support0 libldap-2.4-2 libltdl7 libmagic1 libmnl0 libmpdec2
libnettle6 libnfnetlink0 libp11-kit0 libperl5.22 libpopt0 libpython3-stdlib
libpython3.5-minimal libpython3.5-stdlib libroken18-heimdal librtmp1
libsasl2-2 libsasl2-modules libsasl2-modules-db libsqlite3-0 libssl1.0.0
libtasn1-6 libwind0-heimdal libx11-6 libx11-data libxau6 libxcb1 libxdmcp6
libxext6 libxmuu1 libxtables11 linux-base mime-support netbase
openssh-client openssl patch perl perl-modules-5.22 python3 python3-minimal
python3.5 python3.5-minimal rename rsync udev xauth xz-utils
0 upgraded, 98 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.1 MB of archives.
After this operation, 213 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libatm1 amd64 1:2.5.1-1.5 [24.2 kB]
...
Get:4 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libssl1.0.0 amd64 1.0.2g-1ubuntu4.1 [1122 kB]
Get:5 http://apt.dockerproject.org/repo ubuntu-xenial/main amd64 docker-engine amd64 1.11.1-0~xenial [14.5 MB]
Get:6 http://archive.ubuntu.com/ubuntu xenial/main amd64 libpython3.5-minimal amd64 3.5.1-10 [521 kB]
...
Get:98 http://archive.ubuntu.com/ubuntu xenial/main amd64 xz-utils amd64 5.1.1alpha+20120614-2ubuntu2 [78.8 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 41.1 MB in 25s (1593 kB/s)
Selecting previously unselected package libatm1:amd64.
(Reading database ... 7253 files and directories currently installed.)
Preparing to unpack .../libatm1_1%3a2.5.1-1.5_amd64.deb ...
...
Selecting previously unselected package docker-engine.
Preparing to unpack .../docker-engine_1.11.1-0~xenial_amd64.deb ...
Unpacking docker-engine (1.11.1-0~xenial) ...
...
Unpacking xz-utils (5.1.1alpha+20120614-2ubuntu2) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libatm1:amd64 (1:2.5.1-1.5) ...
...
Setting up docker-engine (1.11.1-0~xenial) ...
invoke-rc.d: policy-rc.d denied execution of start.
Setting up liberror-perl (0.17-1.2) ...
...
Updating certificates in /etc/ssl/certs...
173 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
---> 33697b8b61da
Removing intermediate container 11363734857d
Step 5 : RUN docker -v
---> Running in 8fb0042eaf1c
Docker version 1.11.1, build 5604cbe
---> c5128ef75047
Removing intermediate container 8fb0042eaf1c
Successfully built c5128ef75047 |
|
Discussing this with @tianon and @tiborvass - most likely suspects are corporate firewall, or CDN/transparent proxy (like apt-cacher-ng), but none of us is able to reproduce so far |
|
oh, lol, see @tianon just commented :-) |
meetupwayne
commented
May 11, 2016
|
Ive seen this succeeed and fail. In the case where it has failed. It was a physical machine, I followed the documented Docker install instructions. In the cases where it succeeded both were on virtual machines one was a virtual box VM and other was a VM in Google Cloud platform. Both the physical machine and Virtual Box VM are on the same network. |
zabzal
commented
May 11, 2016
|
I Have also been seeing this issue for the last couple of days.I am using Vagrant shell provisioning to run
Up unit 5/6/16, I was able to provision my Ubuntu Trusty VM (Virtual Box) using this script. As of 5/6/16, I started getting:
I am operating behind a firewall and proxy. Using my company's proxy credentials I have been able to set up docker this way for the past few months without issue. |
|
May be I didn't make it specific enough, for me it fails in AWS. I've used |
hamid-elaosta
commented
May 11, 2016
|
Can somebody try reproduce my fix? I deleted the key, cleaned apt cache and updated again. This errors about missing key so I copied the missing key shown by apt and added it usimg the command from the instructions (note it's a different hex string). Apt update again and suddenly it worked. |
hamid-elaosta
commented
May 11, 2016
|
Oh, also, I found out I run behind squid proxy but it shouldn't affect my traffic, especially not HTTPS. Also, these four machines are the only instance of this happening to me. |
iEmiya
commented
May 17, 2016
|
I am using this: It worked. |
tbenst
commented
May 25, 2016
|
Here was the solution for me, similar to iEmiya:
|
hamid-elaosta
commented
Jun 1, 2016
|
I am trying to install a new VM on Digital Ocean with Xenial and have the same problem, I have tried both the documented version and @iEmiya version (using ubuntu keyserver). Since this time I'm installing from DO, I rule out any squid proxy or cache within my corporate environment. Can @iEmiya and @tbenst confirm they're using the Xenial repository? It's the only repo I have this issue on. Also, @iEmiya Didn't show the commands to the point of installing docker-engine. I'd like to point out that the apt update works fine with the key from either keyserver, it's installing docker-engine that fails to install due to being unable to authenticate. I still suspect the Xenial packages are mis-signed or signed with some other key? |
hamid-elaosta
commented
Jun 1, 2016
|
So this is the key in question; If you install it using the fingerprint as documented here "Update your apt sources", section 4; The If you then remove the key and install it again using; Importantly, using the Hopefully this can point us at the cause. |
|
@hamid-elaosta which region did you run on on DigitalOcean? Here's what I did;
After that, running |
hamid-elaosta
commented
Jun 1, 2016
|
Hi @thaJeztah I ran it on LON1, using the 2GB and Ubuntu 16.04 x64 I added the Xenial repository to /etc/apt/sources.list.d/docker.list and the key imports mentioned above then the update and install. |
|
Did you install |
tbenst
commented
Jun 1, 2016
|
Hi Hamid, yes I was on the default xenial repos Tyler Benster | tylerbenster.com On Wed, Jun 1, 2016 at 10:00 AM, Sebastiaan van Stijn <
|
hamid-elaosta
commented
Jun 3, 2016
|
@thaJeztah Initially, the machines I had the issue with had them installed and up-to date already when I attempted to install them. I installed a fresh machine and installed those packages (they were missing this time) and it worked. However, I've just tried with another machine (clean install of Xenial on a physical server) which had those packages installed already after a fresh install/upgrade and it worked as expected. I'm no more clear on what the cause is/was than when I started. |
hamid-elaosta
closed this
Jun 3, 2016
hamid-elaosta
reopened this
Jun 3, 2016
errordeveloper
referenced this issue
in kubernetes/kubernetes-anywhere
Jun 4, 2016
Closed
[WIP/RFC] Bootstrap EC2 with Ansible #115
|
I am still seeing this in EC2, has anyone else attempted to reproduce in EC2? |
megahall
commented
Jun 7, 2016
|
I can see it when I am configuring from raw Xenial ISOs inside of a Packer based Linux VM Image bootstrap procedure. I am working on narrowing down the cause. |
megahall
commented
Jun 7, 2016
•
Edited 1 time
-
megahall
Jun 7, 2016
-
Jun 7, 2016
|
It seems like it can be prevented by ensuring all of the following commands are run before the |
codepainters
commented
Jun 13, 2016
•
Edited 1 time
-
codepainters
Jun 13, 2016
-
Jun 13, 2016
|
I just encountered the very same problem. I managed to reproduce it under 16.04 VM. If I do the following, the problem doesn't appear: apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
echo "deb https://apt.dockerproject.org/repo ubuntu-xenial main" > /etc/apt/sources.list.d/apt_dockerproject_org_repo.list
apt-get update
apt-get install docker-engineHowever, I can reproduce this problem in a fresh VM if I add the repo first, and only add the key after echo "deb https://apt.dockerproject.org/repo ubuntu-xenial main" > /etc/apt/sources.list.d/apt_dockerproject_org_repo.list
# here it complains about missing F76221572C52609D key
apt-get update
apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
# this second update changes nothing (albeit it doesn't complain about keys anymore)
apt-get update
# apt-get install complains now (I abort here)
apt-get install docker-engineOnce it gets into this state, the only way to recover seems to be manually removing apt cache files: rm /var/lib/apt/lists/apt.dockerproject.org_repo_dists_ubuntu-xenial_*
apt-get update
# and now it works
apt-get install docker-engineIt appears to me to be some |
megahall
commented
Jun 13, 2016
|
Good catch. It might be wise to report this to the Debian / Ubuntu developers. On Mon, Jun 13, 2016 at 09:25:52AM -0700, Przemys??aw W??grzyn wrote:
|
This was referenced Jul 6, 2016
|
@codepainters so it sounds like cloudinit also needs a fix (see my snippet in docker#22599 (comment))... |
100%. Has anyone does this already? |
codepainters
commented
Jul 13, 2016
|
I haven't, I was way too busy those days. I'll try to check it with Debian, and then perhaps fill the ticket before next week. I'll post an update here. |
codepainters
commented
Jul 13, 2016
|
Hmm, something must have changed in the meantime - I can no longer reproduce it under Ubuntu 16.04 VM. Can anyone confirm? |
|
I'm still seeing this - is the base image going to get a refresh of keys? @tianon ? |
roshan3133
commented
Aug 1, 2016
•
Edited 1 time
-
roshan3133
Aug 1, 2016
-
Aug 1, 2016
|
Getting same issue not getting pubkey for ubuntu 16.04 LTS |
|
@jamtur01 @roshan3133 is this an issue with the workaround mentioned above, where you import the key before adding the repository? |
|
@justincormack Hi! The issue for me if that I shouldn't have to use the workaround at all and the base image should get an update. |
hamid-elaosta
commented
Sep 1, 2016
|
@codepainters On a fresh 16.04.1 it no longer happens if I forget to at the key first. I just add it then apt update and it installs like normal. |
roshan3133
commented
Sep 1, 2016
|
Ok... will check that On 1 Sep 2016 14:16, "Hamid" notifications@github.com wrote:
|
|
@jamtur01 not sure I understand what you're suggesting -- are you suggesting that we add Docker's APT repo key into the |
|
It seems that this one can be closed now: the issue is resolved for most, and doesn't seem like something that we can solve at our level. Please let me know if I'm missing something! Thank you all for reporting. |
icecrime
closed this
Sep 20, 2016
lkraider
commented
Jan 20, 2017
|
Website instructions are wrong, here is what works in 16.04: |
pettyalex
commented
Jan 20, 2017
|
Thanks, @lkraider I just stubbed my toe on this setting up a new machine after 1.13 launch. Website needs to be updated. |
|
docs should be fixed now, apologies for the inconvenience! And thanks @lkraider for helping out here! |
alarv
commented
Feb 26, 2017
|
If your distro is Linux Mint, pay attention to this warning in the official docker repos:
Currently, |
T-vK
commented
Mar 16, 2017
•
Edited 1 time
-
T-vK
Mar 16, 2017
-
Mar 16, 2017
|
For Linux Mint 18 this fixed it for me: |
abdihakiim
commented
Oct 27, 2017
|
replace your source.list with this deb http://repo.kali.org/kali kali-rolling main contrib free |
hamid-elaosta commentedMay 9, 2016
•
Edited 1 time
-
hamid-elaosta
May 9, 2016
I have 4 brand new, out of the box pieces of hardware, I've installed Xenial 16.04 on them and updated all packages.
Having added the key for docker and the xenial package repository and attempted to install docker-engine on each of the four machines, I get the following error;
Is the package in the Xenial repository not signed?