You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the latest gVisor release (release-20240916.0) is breaking the development branch of Dangezone. I believe this is the case due to the following:
Our tests have been failing since 5 days ago, when the newest binaries for gVisor were released.
I have rebuilt the v0.7.0 image for Dangerzone, which should run properly on all of our supported platforms, and I get an error as well.
The gVisor error we're seeing when running the container by hand is this:
I0923 13:05:11.356492 1 main.go:201] **************** gVisor ****************
W0923 13:05:11.358402 1 boot.go:266] Not setting product_name: open /sys/devices/virtual/dmi/id/product_name: no such file or directory
I0923 13:05:11.358522 1 boot.go:279] Setting host-shmem-huge: "never"
W0923 13:05:11.359241 1 specutils.go:129] noNewPrivileges ignored. PR_SET_NO_NEW_PRIVS is assumed to always be set.
I0923 13:05:11.359297 1 chroot.go:92] Setting up sandbox chroot in "/tmp"
W0923 13:05:11.359386 1 chroot.go:109] Failed to copy /etc/localtime: open /etc/localtime: no such file or directory. UTC timezone will be used.
I0923 13:05:11.359425 1 chroot.go:37] Mounting "proc" at "/tmp/proc"
W0923 13:05:11.359477 1 util.go:64] FATAL ERROR: error setting up chroot: error mounting proc in chroot: error mounting "proc" at "/tmp/proc": mount("proc", "/tmp/proc", 15) failed: operation not permitted
error setting up chroot: error mounting proc in chroot: error mounting "proc" at "/tmp/proc": mount("proc", "/tmp/proc", 15) failed: operation not permitted
D0923 13:05:11.360661 12 sandbox.go:1330] Destroying sandbox "dangerzone"
You can find the full error report here: gvisor.log. I'll give it a check with the previous gVisor release as well.
The text was updated successfully, but these errors were encountered:
It seems that the latest gVisor release (
release-20240916.0
) is breaking the development branch of Dangezone. I believe this is the case due to the following:The gVisor error we're seeing when running the container by hand is this:
You can find the full error report here: gvisor.log. I'll give it a check with the previous gVisor release as well.
The text was updated successfully, but these errors were encountered: