Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update script to use .asc, remove gpg as pre-requisite #391

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jan 26, 2024

Current distro versions now allow the GPG key to be stored as an .asc file, which simplifies installation. Changing the file extension for the GPG key to .asc lets apt-get know the GPG key is in ASCII armor format, in which case there is no need to "dearmor", and we no longer need gpg as a pre-requisite. Instructions for manual installation on Debian based distros were updated in our documentation through docker/docs@33befd6.

It's common for users to install packages in a combination of the convenience script and manual (e.g. to update the packages after install, or vice-versa). Given that both the script and the manual steps configure the repository, we want those steps to align, otherwise (potentially?) warnings / errors may occur;

$ sudo apt-get update
E: Conflicting values set for option Signed-By regarding source https://download.docker.com/linux/debian/ bullseye: /usr/share/keyrings/docker-ce-archive-keyring.gpg != /usr/share/keyrings/docker-archive-keyring.gpg
E: The list of sources could not be read.

In either case; let's make sure that our script aligns with the manual steps that we document.

Current distro versions now allow the GPG key to be stored as an `.asc` file,
which simplifies installation. Changing the file extension for the GPG key
to .asc lets apt-get know the GPG key is in ASCII armor format, in which case
there is no need to "dearmor", and we no longer need gpg as a pre-requisite.
Instructions for manual installation on Debian based distros were updated in
our documentation through [docker/docs@33befd6].

It's common for users to install packages in a combination of the convenience
script and manual (e.g. to update the packages after install, or vice-versa).
Given that both the script and the manual steps configure the repository, we
want those steps to align, otherwise (potentially?) warnings / errors may occur;

    $ sudo apt-get update
    E: Conflicting values set for option Signed-By regarding source https://download.docker.com/linux/debian/ bullseye: /usr/share/keyrings/docker-ce-archive-keyring.gpg != /usr/share/keyrings/docker-archive-keyring.gpg
    E: The list of sources could not be read.

In either case; let's make sure that our script aligns with the manual steps
that we document.

[docker/docs@33befd6]: docker/docs@33befd6

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah self-assigned this Jan 26, 2024
@thaJeztah thaJeztah marked this pull request as ready for review January 26, 2024 14:13
@thaJeztah thaJeztah requested review from tianon-sso and a team January 26, 2024 14:14
Copy link
Contributor

@vvoland vvoland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Copy link
Member

@tianon-sso tianon-sso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, if I review from here I can merge too. 👍

Hah nope, tricked me!

@thaJeztah thaJeztah merged commit 30c34cc into docker:master Feb 7, 2024
9 checks passed
@thaJeztah thaJeztah deleted the gpg_asc branch February 7, 2024 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

getting warning apt-key parsing
5 participants