这是indexloc提供的服务,不要输入任何密码
Skip to content

[FEAT]: Add configurable --no-sandbox flag for Chromium/Puppeteer on unsupported kernels (e.g. Synology DSM) #3999

@Sarmingsteiner

Description

@Sarmingsteiner

What would you like to see?

On Synology DSM devices, the custom Linux kernel obviously does not support Chromium’s native SUID sandbox. As a result, Anything LLM’s collector process fails to launch Chromium/Puppeteer with the following error:

[collector] error: Failed to scrape https://www.xyz.com. Error: Failed to launch the browser process!
[FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see …
If you want to live dangerously … try using --no-sandbox.

So far, not a single attempt - neither manual Docker entrypoint overrides nor command overrides - has been successful in reliably suppressing the sandbox error message.

It would be extremely helpful to expose a setting (e.g. ANYTHINGLLM_CHROME_FLAGS or similar) so that users on unsupported platforms can simply toggle sandboxing off without forking or rebuilding the container image.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions