Unknown Error Code '125' on Windows and macOS

[apyrgio]

This bug affects new Dangerzone users on Windows and macOS, who have done a fresh installation of Docker Desktop 4.30.0 or greater. We believe that almost all of our new users after August 29th are affected.

Explanation

Docker Desktop 4.30.0, released in August 29th, introduced the following breaking change:

Fresh installations of Docker Desktop now use the containerd image store by default.

When Dangerzone attempts to load its container image tarball in an installation which has enabled the containerd image store, then Docker will report a different image ID than the expected one:

Expected: 099204f90b54
Got: c0865729b351

Dangerzone will fail the container image installation, and subsequent conversions will fail with error code 125.

Workaround

A workaround in this case is to disable the containerd image store from the Docker Desktop settings. This does not pose any security risk or loss of functionality for the Dangerzone users.

Open Docker Desktop, go to Settings (gear icon) -> General (scroll down) -> Unselect "Use contained for pulling and storing images" -> click on "Disable containerd" in the pop-up window -> click on "Apply & restart".

Follow this issue for updates and an official fix.

[spkerber]

Confirming that this update worked for me! Thank you + much appreciated!
Easier than stashing the terminal command for each use.

[charginglabrador]

Unfortunately, this workaround hasn't worked for me. When I went to the settings, containerd was already disabled. I tried re-enabling, restarting Docker, and then disabling and restarting, but with the same outcome.

[apyrgio]

Good to know @charginglabrador. I think you're bit by an extra issue actually, check out my comment here: #919 (comment)

[apyrgio]

We're happy to inform you that we have released Dangerzone 0.7.1, which should fix this problem on Windows and macOS platforms. Try it out, and let us know if something is amiss.