apt-key no longer available on ubuntu 25.04

[scoopex]

Describe the Bug

When adding a apt key the module puppetlabs-docker failes because the tool "apt-key" is no longer part of ubuntu apt.
"apt::source" or "apt::key" seems to rely on that tool.

The tool is not delivered anymore by ubuntu packages.

Expected Behavior

Remove the dependency to apt-key and keep the signatures to not break existing modules.

Steps to Reproduce

Use a source defined like that on Ubuntu 25.04.

apt::source { 'docker':
  location     => $location,
  architecture => $architecture,
  release      => $release,
  repos        => $package_repos,
  key          => {
    id     => $package_key,
    source => $key_source,
  },
  include      => {
    src => false,
  },

Environment

• Puppet 8
• Ubuntu 25.04

[kenyon]

This is a problem in puppetlabs-docker, not puppetlabs-apt. It would be fixed by puppetlabs/puppetlabs-docker#965.

[scoopex]

Sure, it would be a good idea to use modern key mechanisms.

But breaking existing APIs/Functionality should be a no-go, especially for modules which are used in some many projects.
Why do you not replace the implementation by something which does not have dependencies to "apt-key"?

[kenyon]

Why do you not replace the implementation by something which does not have dependencies to "apt-key"?

That is what puppetlabs/puppetlabs-docker#965 does.

[scoopex]

Why do you not replace the implementation by something which does not have dependencies to "apt-key"?

That is what puppetlabs/puppetlabs-docker#965 does.

No, because puppetlabs/puppetlabs-docker is not the only project which uses apt::key.

[kenyon]

Why do you not replace the implementation by something which does not have dependencies to "apt-key"?

That is what puppetlabs/puppetlabs-docker#965 does.

No, because puppetlabs/puppetlabs-docker is not the only project which uses apt::key.

I don't think you are understanding the problem here. But if you have a better solution, feel free to create a pull request.

[scoopex]

My understanding of the situation is:
"apt::key” is a functionality of this Puppet module that uses the command line tool ‘apt-key’ in the background.

Due to nonavailability of this as of Ubuntu 25.04, adding keys in this way no longer works and some Puppet modules will have problems with it based on this behavior. There seems to be an alternative way, but it will create significant effort for Puppet users and the maintainers of packages that use this mechanism in all packages that use the previous mechanism. Wouldn't it be a good idea to keep the old behavior functional with a deprecation warning in addition to the new one, as this could avoid some trouble?

Have I overlooked something?

[kenyon]

I don't see how you could use the new keyring method while keeping the puppetlabs-apt interface unchanged, but you are two years too late for that design work: #1105

Almost all of the puppet ecosystem has already migrated to the "modern keyring" method provided in puppetlabs-apt 9.2.0, so the "significant effort" is mostly already done. It's just some poorly-maintained modules like puppetlabs-docker that are lagging behind, but that's no surprise given that the company behind puppetlabs is actively trying to destroy the community and ecosystem. (Note: OpenVox is the replacement for open source Puppet.)

[scoopex]

Ah thanks for the information. I am currently only using Puppet to maintain my Linux desktops system at home and for working (but used it 4 years ago extensively). Thanks for describing the situation, that is understandable but now breaks.
I will make a pull request to the docker module or will search a better maintained module.