-
Notifications
You must be signed in to change notification settings - Fork 172
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
Latest gVisor release breaks Dangerzone #928
Labels
bug
Something isn't working
Comments
Yeap, building Dangerzone with the 2024-08-26 gVisor release works. The change I made was: diff --git a/Dockerfile b/Dockerfile
index 9988660..872e634 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -88,7 +88,7 @@ FROM alpine:latest
RUN apk --no-cache -U upgrade && \
apk --no-cache add python3
-RUN GVISOR_URL="https://storage.googleapis.com/gvisor/releases/release/latest/$(uname -m)"; \
+RUN GVISOR_URL="https://storage.googleapis.com/gvisor/releases/release/20240826/$(uname -m)"; \
wget "${GVISOR_URL}/runsc" "${GVISOR_URL}/runsc.sha512" && \
sha512sum -c runsc.sha512 && \
rm -f runsc.sha512 && \ I'll open an issue in the gVisor tracker, in case someone has encountered something similar. Edit: opened google/gvisor#10944. |
apyrgio
added a commit
that referenced
this issue
Sep 26, 2024
Temporarily pin gVisor to the latest working version (`release-20240826.0`), since the latest one breaks our container image. Refs #928
apyrgio
added a commit
that referenced
this issue
Sep 27, 2024
Temporarily pin gVisor to the latest working version (`release-20240826.0`), since the latest one breaks our container image. Refs #928
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: