Alexis Métaireau

Hi @sudwhiwdh. As @apyrgio isn't around this week I'm taking the relay. Thanks for opening this issue and keep us informed about how this worked for you. > I have...

Hi @develorer and sorry you haven't had an answer sooner. We currently rely quite heavily on docker containers in the current form of Dangerzone. That being said, the "isolation provider"...

That would be great! Did you manage to solve your issue?

Just noting that this is currently put on hold, waiting for #1080 to be merged and 0.9.0 to be released, as it will be much easier to package for upstream...

Hey, thanks for opening an issue. Unfortunately Windows on ARM is currently not a supported platform, hence why you're seeing errors. The error you're seeing seem to be gvisor blocking...

A PR has been opened by @apyrgio upstream and we're waiting on their feedback. See https://github.com/containers/podman-py/pull/558 for more details.

Note: Cosign bundling is now basically done now in this `independent-container-updates` branch, alongside some packaging work that was needed to get the new `dangerzone-image` tool to be available to all...

> * I still hope we revisit the Dangerzone icon eventually, but with the current icon, the "warning" connotation is IMO especially problematic in a message prompt like this. It...

The tests are now green on this branch (you can see this [here](https://github.com/almet/dangerzone/pull/1/checks)), and I rebased everything in a series of only 18 commits (from almost 200+ commits in total...

If/When we ship the content inside the branch, it will break main, because the archives produced are not able to be loaded by Docker. It's okay and something we do...