Alex Pyrgiotis

I took the liberty to make some rewordings in the PR, in a separate fixup commit. Also, I've commented on the original issue about our change of course on this...

Good to know @charginglabrador. I think you're bit by an extra issue actually, check out my comment here: https://github.com/freedomofpress/dangerzone/issues/919#issuecomment-2382396930

We're happy to inform you that we have [released Dangerzone 0.7.1](https://github.com/freedomofpress/dangerzone/releases/tag/v0.7.1), which should fix this problem on Windows and macOS platforms. Try it out, and let us know if something...

Hi @andersonesque, thanks a lot for the bug report. We'll figure this out together. Can you tells us some more info about your environment? 1. What is your macOS version...

Awesome, thanks for the info, and the screenshot looks great. You can copy-paste text as well if you want, and add it here between ` ``` ` tags. The fact...

HI @charginglabrador! Thanks a lot for chiming in. Let's see what's the case in your installation. If you're comfortable with the CLI, can you please run these Docker commands, so...

Hi @phillipmcmahon. It seems that lots of people have started to pile up on this issue, so let's reopen it. Can you perhaps run the commands I mentioned to @charginglabrador...

I see. Your logs look indeed similar to the original poster. What happens if you run: ``` gunzip -c /Applications/Dangerzone.app/Contents/Resources/share/container.tar.gz | docker load ``` Also, what happens if you uninstall...

It seems that this issue affects users who have installed from scratch Docker Desktop 4.30.0 or greater. Everyone who's affected, please read https://github.com/freedomofpress/dangerzone/issues/933 for an explanation and a workaround.

Great, thanks for the command output. You're in the latest Docker Desktop version, so check https://github.com/freedomofpress/dangerzone/issues/933 for a workaround.