-
Notifications
You must be signed in to change notification settings - Fork 313
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
[Bug] debian 11/ubuntu 22.04 need to handle apt-source differently #884
Comments
Would like to have this merged, please. |
Is this going to be merged anytime soon? |
The code by itself is done but testing/ linting is failing at the moment. @xRoyalz please feel free to contribute :) |
I have exactly zero time and interest on opening a proper pull request but I like to help people sooo... I fixed this bug by commenting out the section below: Replacing it by
YMMV tho! xD |
#965 fixes this. |
Since Ubuntu 22.04 / Debian 11 apt-key is deprecated. Storing gpg-keys in /etc/apt/trusted.gpg (default behavior) is now producing warnings.
Also it is not longer recommended to get the gpg-keys via keyserver for security purposes.
The recommended way is to provide the gpg-key in /etc/apt/keyrings/KEY.gpg and add '[ signed-by = PATH ]' to the docker.list-file.
The puppetlabs/apt-Module has already implemented the new way of key handling via #991.
In my opinion the docker::repos class has to handle releases above Ubuntu 22.04 and Debian 11 different.
The text was updated successfully, but these errors were encountered: