-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
"--no-sandbox" incorrectly parsed as a file? #1056
Comments
Hi, Same behaviour using a Debian 11.3 container and Draw.io 19.0.3. Here are the logs: $ drawio --border=0 --export --no-sandbox --output diagrams/schema.png --page-index=3 \
diagrams/schema.drawio
[20489:0802/112631.689242:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[20489:0802/112632.026361:ERROR:ozone_platform_x11.cc(248)] Missing X server or $DISPLAY
[20489:0802/112632.026380:ERROR:env.cc(226)] The platform failed to initialize. Exiting.
The futex facility returned an unexpected error code.
make: *** [Makefile:164: diagrams/schema.png] Aborted (core dumped) |
A solution for this is to have #249 (comment) (a previous issue which was closed, probably because it got slightly derailed) As for the "preferred" way to script this, as far as I know the recommendation is either to use Xvfb or to use the web server to export it (as recommended #127 (comment)) |
Still there in the latest release. drawio --border=0 --export --no-sandbox --output test.png lifecycle-original-draw-io.svg gives
|
Thanks for the report. It will be fixed in the next release. |
In 24.5.3. |
@davidjgraph do you have a reference to the individual commit that fixed the issue? |
No, it wasn't made in a public repo. |
Seems to be 32badd8 by @m-mohamedin |
Preflight Checklist
Describe the bug
I'm trying to run drawio on CI, in a docker container. I have to add
--no-sandbox
to get it to almost start. However, it then dies with "Error: input file/directory not found". I suspect it's trying to treat--no-sandbox
as another file to process, but am not 100% sure.To Reproduce
Steps to reproduce the behavior:
drawio --export --format pdf --embed-diagram --output architecture.drawio.pdf architecture.drawio
as a normal user, not in docker: it should work if you have an "architecture.drawio" file.drawio --no-sandbox --export --format pdf --embed-diagram --output architecture.drawio.pdf architecture.drawio
Expected behavior
It should run, but without using the sandboxing features from electron
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):
Desktop (please complete the following information):
Additional context
If there's an alternate preferred way to script this, I'd be happy to hear it, especially since using the desktop deb requires an Xvfb fake X server, asound, etc: lots of things that the actual command-line usage shouldn't probably use, but which are getting pulled in by being part of a larger app.
The text was updated successfully, but these errors were encountered: