-
Notifications
You must be signed in to change notification settings - Fork 181
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
Invalid JSON from container when trying to open input file #400
Comments
Interesting. I've seen this error when the source file ( So, my guess is that somehow, Dangerzone does create a temporary directory, but never copies the file to that directory. Which is weird, since we would have caught it during testing. Do you have any more info that can help us here?
|
So on my machine i have TMPDIR=/var/folders/yc/2v_c... so it definitely thinks it wrote something there.
if I change the setting to allow the dev/ directory docker can mount it. However running Dangerzone continues to use the temp dir running the container manually with the dev/ path seems to work until
conclusions: so for whatever reason it looks like I wasn't sharing any directories with docker so I changed that. sharing the /private/var/folders in the docker settings and running digging into it some... however for me I only needed to share /private/var/folders/ in order to get it to work If possible I think a good fix is checking that docker has the correct folders shared before running. thanks for the help! |
We no longer use temporary directories as of #625, so I believe users will not experience an issue similar to this with the upcoming 0.8.0 release. If that's not the case, feel free to reopen the issue. |
MacOS 13.3.1 / Intel i7
Looks like there are still some issues mounting the input file(s)
I get invalid JSON in both the gui and cli
IsADirectoryError: [Errno 21] Is a directory: '/tmp/input_file'
I've given docker and Dangerzone full filesystem access
which docker -> /usr/local/bin/docker
when running the gui I see containers being made and destroyed rather quickly in Docker Desktop as well.
Related Issues:
#335
#371
The text was updated successfully, but these errors were encountered: