Repository navigation
Documentation on adding download.docker.com/linux/debian as debian repo not working #16626
Description
File: engine/install/debian.md
Hi,
I followed the instructions how to add download.docker.com/linux/debian as debian repo but I cannot get it to work.
The error is when running apt update:
Get:3 https://download.docker.com/linux/debian bullseye InRelease [43.3 kB]
Err:3 https://download.docker.com/linux/debian bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
I did setup the repo as below:
$ sudo mkdir -p /etc/apt/keyrings
$ curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
I checked that the key was there and it has the correct format.
Then I did:
$ echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
This results in the following file:
$ cat /etc/apt/sources.list.d/docker.list
deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian bullseye stable
I also tried adding read perms to key but that did not change the error:
$ sudo chmod a+r /etc/apt/keyrings/docker.gpg
I also tried to import the particular key id manually but then I got:
$ gpg --keyring /etc/apt/trusted.gpg --recv-keys 7EA0A9C3F273FCD8
gpg: key 8D81803C0EBFCD88: "Docker Release (CE deb) <docker@docker.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Activity
thaJeztah commentedon Jan 30, 2023
I tried the steps from the documentation, but wasn't able to reproduce the issue;
After this, docker is installed;
Did you have docker installed before this? Or was this on a fresh system?
ArnoSen commentedon Jan 30, 2023
This is a fresh system.
ArnoSen commentedon Jan 30, 2023
I am running a fully updated version Debian 11.
ArnoSen commentedon Jan 30, 2023
(BTW: interesting to talk to you after so many years! I am your old friend from Lisse living at the Heereweg. We spent quite some time together in the old days! Good to talk to you again! I hope you are doing well!)
thaJeztah commentedon Jan 30, 2023
Oh, wow! That's been a really long time! I'm doing fine; how you are doing good as well!
Hm.. interesting; so I tried it on a fresh droplet on DigitalOcean; kernel version there is (although I doubt kernel version should be related to this 🤔)
We do get a lot of installs on Debian, so it doesn't appear to be a "general" issue, but definitely possible that there's something that depends on how the system is configured. Now the fun bit: discovering what could trigger this.
I see there was at least one report were permissions of the directory also had to be updated (no idea if it resulted in the same issue though); see #16362
ArnoSen commentedon Jan 30, 2023
Doing fine here!
I did some more testing. The directory permissions are indeed the culprit! And yes, the solution provided in #16362 solve the problem. Thanks for your help!
Please give my regards to Edwin and your parents!
ArnoSen commentedon Jan 30, 2023
When reading https://wiki.debian.org/DebianRepository/UseThirdParty, it mentions the required directory permissions:
The above
SHOULDshould be read asMUST.thaJeztah commentedon Feb 7, 2023
Oh! Completely forgot to reply!
I did, and told them that I "ran into you". They're all doing well, and said "hi!"
Great to hear that that fixed the issue! 🎉
ArnoSen commentedon Feb 7, 2023
Good to hear from them!
I am closing the issue.
docker-robott commentedon Mar 25, 2023
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked