Port to macOS about dangerzone HOT 4 CLOSED

what the benefits of podman over docker?

from dangerzone.

The two big benefits in my mind are:

• podman doesn't require a daemon, so its architecture is much simpler, has smaller attack surface (there's various ways a badly configured docker daemon could be used for privilege escalation), and is portable -- you can just basically ship the podman binary, and then use it to run containers
• podman allows for running containers without root (though the containers themselves still have a root user), so an unprivileged user can start the container, doesn't need to type a password, etc.

All that said, docker would work fine too, and it would be much simpler to get running on macOS if the user has Docker for Mac installed. Also, it looks like the podman remote client doesn't work without root yet anyway.

Ideally though, dangerzone will be a self-contained app, so you can install dangerzone and then just use it, without needing to separately install Docker for Mac and keep it updated. Maybe that could be a long-term goal though, and in the short-term it could try to find docker and use it if it's installed...

from dangerzone.

Oh yeah one more issue with making dangerzone work for macOS is the "Open safe document after converting" feature. Right now the Common._find_pdf_viewers function discovers the list of apps installed that can open application/pdf MIME types, but it's Linux-only. It basically searches for .desktop files in the right places and parses them, but this process is totally different in macOS, so it will have to detect the OS and work differently.

from dangerzone.

The master branch now works enough in macOS to run, using Docker for Mac! I'm closing this issue in favor of two smaller ones (#2, #3).

from dangerzone.