Docker build fails with GPG error finding public key 467B942D3A79BD29

[jrzerr]

I build and the error I get is

W: GPG error: http://repo.mysql.com/apt/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
E: The repository 'http://repo.mysql.com/apt/debian buster InRelease' is not signed.
The command '/bin/sh -c { 		echo mysql-community-server mysql-community-server/data-dir select ''; 		echo mysql-community-server mysql-community-server/root-pass password ''; 		echo mysql-community-server mysql-community-server/re-root-pass password ''; 		echo mysql-community-server mysql-community-server/remove-test-db select false; 	} | debconf-set-selections 	&& apt-get update 	&& apt-get install -y 		mysql-community-client="${MYSQL_VERSION}" 		mysql-community-server-core="${MYSQL_VERSION}" 	&& rm -rf /var/lib/apt/lists/* 	&& rm -rf /var/lib/mysql && mkdir -p /var/lib/mysql /var/run/mysqld 	&& chown -R mysql:mysql /var/lib/mysql /var/run/mysqld 	&& chmod 1777 /var/run/mysqld /var/lib/mysql' returned a non-zero code: 100

To reproduce:

• clone fresh repo
• cd mysql/8.0
• docker build -f Dockerfile.debian .
• You get an error above with the public key missing

I can't find that key anywhere on several public key servers I've looked on, mit, ubuntu, openpgp

I am building on popos but also having the error building out in Gitlab CI. So it's not just my own machine.

The last record I have of this working is 3 days ago. But we didn't start back up working until today, so can't figure out the exact timing.

[matrak-jason]

We are seeing this too at my company. It seems like it must be related to this issue #801 however in that issue, the date they mention is in February.

[jrzerr]

I stumbled across that too, thought that might be the problem, but it didn't fix anything. If I apply the same new key in that PR I get this error instead because I suspect that the new version isn't published yet. Honestly don't know what's going on. But think you are on the right path.

E: Version '8.0.27-1debian10' for 'mysql-community-client' was not found
E: Version '8.0.27-1debian10' for 'mysql-community-server-core' was not found
The command '/bin/sh -c { 		echo mysql-community-server mysql-community-server/data-dir select ''; 		echo mysql-community-server mysql-community-server/root-pass password ''; 		echo mysql-community-server mysql-community-server/re-root-pass password ''; 		echo mysql-community-server mysql-community-server/remove-test-db select false; 	} | debconf-set-selections 	&& apt-get update 	&& apt-get install -y 		mysql-community-client="${MYSQL_VERSION}" 		mysql-community-server-core="${MYSQL_VERSION}" 	&& rm -rf /var/lib/apt/lists/* 	&& rm -rf /var/lib/mysql && mkdir -p /var/lib/mysql /var/run/mysqld 	&& chown -R mysql:mysql /var/lib/mysql /var/run/mysqld 	&& chmod 1777 /var/run/mysqld /var/lib/mysql' returned a non-zero code: 100

[matrak-jason]

It seems one can work around this issue with RUN apt-key adv --keyserver pgp.mit.edu --recv-keys 467B942D3A79BD29

Taken from https://askubuntu.com/a/900936

[jrzerr]

Searching on that key server, that key doesn't exist. Maybe I'm not using it right, but I go to:
http://pgp.mit.edu/

And put in that key name and select the exact match checkbox and it results in "No Results Found"

Additionally, running that command does not work for me. Results in:

Executing: /tmp/apt-key-gpghome.ZhBYlTzw3w/gpg.1.sh --keyserver pgp.mit.edu --recv-keys 467B942D3A79BD29
gpg: keyserver receive failed: No keyserver available

That command takes a very long time to run, a minute or more, that seems odd too. Like maybe there are some issues with the keyserver. Seems like a search like that should expect to respond back pretty quickly.

[matrak-jason]

It may be an issue with how the command is presented in the docker file? The reason I say that is I can't see adv in the command output you posted; but then again it's hard to say without seeing the content of gpg.1.sh

In any case it's only suitable as a workaround and I think the underlying issue is still something that needs addressing by the maintainers

Actually I see now this command fixes some of my containers but not others. Could be dependent on the exact docker image. I guess it shouldn't be considered as a comprehensive workaround.

[hiroshinakasone]

I did a search on pgp.mit.edu using '0x467b942d3a79bd29' and found the key.
http://pgp.mit.edu/pks/lookup?search=0x467B942D3A79BD29&op=index

[Lisible]

I'm encountering the problem too, and the same issue as @jrzerr when trying to fetch the key.
Edit: I managed to fetch the key through the ubuntu keyserver, see the below answer.

[RafaelCapella]

I managed to download the proper Key using ubuntu keyserver with below command:

apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv-keys 467B942D3A79BD29

I have also checked on the pgp and the key does belong to msql:
http://pgp.mit.edu/pks/lookup?search=mysql-build%40oss.oracle.com&op=index&fingerprint=on

There is also mention of this key in the dev.mysql page:
https://dev.mysql.com/doc/mysql-secure-deployment-guide/8.0/en/secure-deployment-verify-package.html

So I have good reasons to believe that the key is correct. I don't understand why its breaking MySQL version lower than 8.0, when the documentation says it should be only needed for MySQL 8.0.28 releases and higher

Click on the keyID link, copy the key, and save it to a file named mysql_pubkey.asc, for example. keyID 3A79BD29 is for MySQL 8.0.28 releases and higher. keyID 5072E1F5 is for earlier MySQL releases.

[jrzerr]

Thanks @RafaelCapella that's working for me... just added:

apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv-keys 467B942D3A79BD29

To my Dockerfile before doing the mysql deb install.

I'm going to leave this open for now, I'll leave it up to someone else to close, because it's a workaround, and the main mysql Dockerfile is broken until the related PR gets merged in. Sounds like some unexpected stuff must have happened here with switching keys and coordinating upstream. And folks like me who built a Dockerfile based on techniques in this repo have to work around. Thanks again for the help everyone.

[tianon]

Yep, this is the same underlying issue as #801 which will be fixed by #808. I'm going to close this in favor of tracking this via #808.

[arjun2038]

I had the same issue.Updating docker to the latest version worked for me