-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown Error Code '125' #919
Comments
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?
|
Hi @apyrgio, thanks for your fast response.
|
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 The fact that Dangerzone stopped working after the upgrade is possible, since we've made an important change in 0.7.0 that has affected some users (in a different way than you though). Let's see if this is the case. From your terminal, can you run the following commands and paste the result here? List all Docker images:
Attempt to convert a dummy file from the terminal:
Attempt to run the Dangerzone container, with debug logs:
|
Great, thanks so much and see below:
|
I'm experiencing the same error as OP above btw (identical OS + dangerzone versions). |
Thanks for the information. For a reason I have yet to understand, Dangerzone fails to install the container image. Can you please report what the following command outputs on your machine(s)? gunzip -c /Applications/Dangerzone.app/Contents/Resources/share/container.tar.gz | docker load And then listing again the images with : docker images Note Because we are able to detect that the container image installation wasn't successful, we should display it to you in the interface. This is tracked by #193 (and hopefully will be solved soon). |
|
Thanks for trying it out. Can you try converting a document with Dangerzone now? (My understanding is that it should work) If that's the case, it might be that the code we're using to gunzip the container image doesn't seem to work well on your machine. Could you please give us a bit more details about your machine? (e.g. what's the specific model and cpu architecture), you can find this in "apple / about" |
After I did this above^, I was able to process a PDF into a safe copy. Machine: MacBook Air (Apple M3), Memory 16 GB, Sonoma 14.6.1 |
Dang, tried again and encountered the same error. Maybe I'm doing something incorrectly because the commenter above had a different experience.
My computer: Model Name: MacBook Air |
@andersonesque thanks for trying this out, and sorry to hear that it didn't solve your problem. Could you please give us what the following command returns? (in backquotes as well): docker info -f 'json' If I was in your case, I would also try uninstalling and re-installing Docker Desktop, to see if the problem goes away. |
Hey, thanks so much ... here's the code. i'll try your suggestion re: Docker and let you know. Thank you for helping me! Editing to add that I purged all data in Docker and completely uninstalled/reinstalled, still having the issue. Thanks
|
Ok! It is now working! I tried uninstall/reinstall one last time and it seemed to do the trick. Thank you all so much for your help! Take care. |
Thanks again from me too! So helpful! |
Glad it helped (even if I still wonder what caused this 👀 ) |
@andersonesque just for the sake of trying to understand and prevent problems for others, could you let me know what the command now returns for you? (So I can compare the outputs before and after reinstallation) docker info -f 'json' |
Yes, a mystery but I'm happy it's now working. There was some integrity issue detected when I was troubleshooting in
|
Thanks for sharing this. Here is a diff between the two outputs. Driver type was 2,3c2,3
<...snip...>
< "Driver": "overlayfs",
---
> "Driver": "overlay2",
11,12c11,28
< "driver-type",
< "io.containerd.snapshotter.v1"
---
> "Backing Filesystem",
> "extfs"
> ],
> [
> "Supports d_type",
> "true"
> ],
> [
> "Using metacopy",
> "false"
> ],
> [
> "Native Overlay Diff",
> "true"
> ],
> [
> "userxattr",
> "false"
<...snip...> I'll leave it here for now, thanks for following-up! |
I'm having the same issue, also on MacOS Sonoma 14.6.1 and Dangerzone 0.7.0. I've tried reinstalling Dangerzone from the website and using Homebrew. Can I provide any more info to help you help me? Thanks! |
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 that we can see its state?
Then try to convert a dummy file from the terminal:
And finally, attempt to run the Dangerzone container, with debug logs:
Thanks a bunch! |
Have the same issue macOS 14.7, latest docker desktop installed. Happy to run whatever you need to get more info to track this down. Let me know. |
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 above? |
phillipmcmahon@mymacbook ~ % docker run hello-world Hello from Docker! To generate this message, Docker took the following steps:
To try something more ambitious, you can run an Ubuntu container with: Share images, automate workflows, and more with a free Docker ID: For more examples and ideas, visit: See attached files. |
|
I see. Your logs look indeed similar to the original poster. What happens if you run:
Also, what happens if you uninstall and reinstall Docker Deskop? |
phillipmcmahon@mymacbook ~ % gunzip -c /Applications/Dangerzone.app/Contents/Resources/share/container.tar.gz | docker load After uninstalling and reinstalling, the same error still persists. |
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 #933 for an explanation and a workaround. |
Docker commandsdocker version:
docker info -f 'json'
docker images
docker run hello-world
Dummy file
Debug logs
|
Great, thanks for the command output. You're in the latest Docker Desktop version, so check #933 for a workaround. |
@charginglabrador: I took a closer look at your debug logs, after your comment, and I spotted this line:
It looks as if you're low on disk space in your machine. Can you perhaps erase some unnecessary files, purge data from Docker Desktop (there's an option for that, if you right-click on the tray icon), and retry? |
Closing this issue, since we released Dangerzone 0.7.1 which should fix it. |
Note that this specific error should be made obvious once #193 is done. |
Hi all, I apologize I am not a developer, but I'm having an issue with the software ... lately, any time I try to convert any document, right away I receive the message "Unknown Error Code '125' ... is there anyone who can help me with this? I am using Macintosh OS with silicon chip.
The text was updated successfully, but these errors were encountered: