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
Error: ActiveDoc initialization failed #177
Comments
Thanks for reporting this! We did change sandboxing in v0.7.7 to turn on by default. You can get the old behavior back by setting I'd be very interested in what is causing this failure. If you still have the error log, is there any chance you could look for an earlier failure? The log pasted just shows a record of the message passed to the client, not the original problem. Are you running Grist within a docker container? |
Thank you @paulfitz and you team for Grist!
Hope I can run |
The The |
@Vladimir-Va I looked at |
I try to reproduce:
part 2. I change slug
|
The earliest problem I see is I realize I copied an environment variable with a typo in an earlier answer. If you'd like to run without attempting gvisor sandboxing, set I didn't follow what you said about slugs, I'm sorry. |
I guess I run into some kind of the same error, because
This is my env:
|
Thanks for reporting that @helmut72. Looks like we'll need to back off sandboxing by default in the docker image, there may be too much variety in security settings. Sorry for the disruption. In other news, @Vladimir-Va the behavior of Grist with |
@helmut72 If you don't mind sharing, what OS and CPU is your host machine running Docker using? Are you by any chance virtualizing Linux (e.g. using Hyper-V on Windows to run Docker)? Asking because the error seems to indicate your CPU is lacking a feature needed by the sandbox (XSAVE). |
I use Ubuntu 20.04 as the Host OS on bare metal and run your Docker Image from hub.docker.com. CPU is a Celeron/Atom, used in many NAS systems. But my PC isn't a NAS.
|
It looks like making gvisor sandboxing the default in our docker image is causing people trouble, so this backs off from that change. We retain gvisor's runsc executable in the image so that turning on sandboxing is just an environment variable setting away. Lack of sandboxing is not good for users opening untrusted documents, so it would be good to be aggressive about turning it on, or communicating about it, so there's follow-up work needed. In the meantime I've updated the documentation about it somewhat. See #177
Thanks @helmut72. Looks like the xsave flag is missing from that CPU, which explains the error from gvisor. We'll push up a fix to disable sandboxing by default. I'm not too sure if there's anything we can adjust in gvisor to work around this though; will need to do more research. |
Thanks @georgegevoian @paulfitz As long as it works without sandboxing, I don't care about sandboxing. |
Hello @helmut72 |
@helmut72 the @Vladimir-Va the latest image also has a fix for |
Hello i resetup new gristlabs/grist:v0.7.7
Log:
.Env:
And maybe is bcs GRIST_SANDBOX=gvisor?
The text was updated successfully, but these errors were encountered: