dangerzone/dangerzone
Alex Pyrgiotis a1402d5b6b
Fix a Podman regression regarding Buildkit images
Loading an image built with Buildkit in Podman 3.4 messes up its name.
The tag somehow becomes the name of the loaded image.

We know that older Podman versions are not generally affected, since
Podman v3.0.1 on Debian Bullseye works properly. Also, Podman v4.0 is
not affected, so it makes sense to target only Podman v3.4 for a fix.

The fix is simple, tag the image properly based on the expected tag from
`share/image-id.txt` and delete the incorrect tag.

Refs containers/podman#16490
2025-03-20 17:17:40 +02:00
..
container_helpers Symlink /usr in Debian container image 2025-01-27 21:40:27 +02:00
conversion Symlink /usr in Debian container image 2025-01-27 21:40:27 +02:00
gui Avoid passing wrong options -B to subprocesses 2025-03-17 17:47:42 +01:00
isolation_provider Fix a Podman regression regarding Buildkit images 2025-03-20 17:17:40 +02:00
__init__.py Add an import preference for vendored packages 2024-10-15 14:58:06 +03:00
args.py Always use sys.exit when exiting the application 2024-05-09 15:57:42 +03:00
cli.py Run ruff format 2025-01-23 14:48:33 +01:00
container_utils.py Fix a Podman regression regarding Buildkit images 2025-03-20 17:17:40 +02:00
document.py Provide sanitized version of output filename 2024-10-17 15:33:58 +03:00
errors.py Factor out container utilities to separate module 2024-12-10 11:31:39 +02:00
logic.py Add a --debug flag to the CLI to help retrieve more logs 2025-01-16 11:35:06 +01:00
settings.py fix: do not catch bare exceptions 2024-06-05 14:19:31 +02:00
util.py Drop Ubuntu 20.04 (Focal) support 2025-03-17 15:40:25 +02:00