Alexis Métaireau

We now have https://stats.dangerzone.rocks. It doesn't count the .deb / .rpm downloads, but that's good enough for now. Closing.

Hi Lasse, thanks for opening this issue. Colima is unfortunately currently not supported and we do not test Dangerzone with it at the moment. We are aware of the licensing...

Adding the `RUNSC_DEBUG=1` environment variable to the docker run invocation with `-e RUNSC_DEBUG=1` got me some more logs: Details ``` $ /opt/homebrew/bin/docker run -e RUNSC_DEBUG=1 --security-opt=no-new-privileges:true --security-opt seccomp=/Users/alexis/Desktop/seccomp.gvisor.json --cap-drop all...

> this likely stems from a difference in permissions between the VM image that Colima uses vs the one Docker Desktop uses. This seems related to https://github.com/abiosoft/colima/issues/267, which points to...

@LasseKrache You can try running colima with `colima start --mount "/tmp:w"` Also, here is how to change the mounts to make this permanent. Can you give it a try and...

Thanks for the follow-up. This "Dangerzone requires Docker Desktop" error is probably due to the fact we're looking for the wrong binaries (because we detect the OS and use different...

Setting the `TMPDIR` env variable (in different ways) doesn't seem to change the produced error message, and doesn't seem to affect the directory that's used by gVisor's [`chroot.go`](https://github.com/google/gvisor/blob/8425e278c51eaec75de310cf3d13cf1e6ae0a05e/runsc/cmd/chroot.go#L90) / [`os.TempDir`](https://pkg.go.dev/os#TempDir)....

We were releasing a hotfix release last week, and haven't got the time to have a look at this until now. Looking at the output of `docker info` when running...

Thanks @EtiennePerot. Running with the latest container doesn't make a difference (I was using the container we shipped with `0.7.1`, which didn't contain the `--directfs=false` from #898). Here is the...

After some more tinkering with @apyrgio, we found that it's possible to make the container work with colima, by doing the following changes: 1. Add `--security-opt: apparmor=unconfined` to the docker...