You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ sudo docker build . -t aptly:0.0.1
$ sudo docker run --entrypoint="" aptly:0.0.1 gpg --version
gpg (GnuPG) 2.2.27
$ sudo docker run --entrypoint="" aptly:0.0.1 gpgv1 --version
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "gpgv1": executable file not found in $PATH: unknown.
ERRO[0000] error waiting for container: context canceled
Context
Packages hosted on Debian and Ubuntu default repositories are not functional.
Possible Implementation
The cleanest way would be to make Aptly work with GPG v2, which has been the default for many years. Fixing the dependencies in the Debian packaging would be a good quick-win though.
However, it requires the additional -keyring option, I guess the reason is that it still tries to find the trustedkeys.gpg file (gpg1 keyring format) by default.
-keyring=trustedkeys.gpg: gpg keyring to use when verifying Release file (could be specified multiple times)
Detailed Description
Per the documentation here, Aptly is only compatible with GPG v1.
However, the dependencies for the packages ( debian, ubuntu) force installation of gnupg which is gpg version 2.
This can be tested by building and running this Dockerfile:
Context
Packages hosted on Debian and Ubuntu default repositories are not functional.
Possible Implementation
The cleanest way would be to make Aptly work with GPG v2, which has been the default for many years. Fixing the dependencies in the Debian packaging would be a good quick-win though.
Your Environment
See Dockerfile above to reproduce
Other
Possibly the same as:
The text was updated successfully, but these errors were encountered: