Playwright fails to execute in code node(FileNotFoundError for driver/node)

[BBBChan]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Deploy Dify on Kubernetes using the official image
2. Update sandbox config: extended allowed_system to large list(0-440) and update python_lib_path as below:

• /usr/local/lib/python3.10/site-packages
• /usr/local/lib/python3.10/site-packages/playwright
• /usr/local/lib/python3.10/site-packages/playwright/driver
• /usr/bin
• /bin
• /tmp
• /dev/shm
• /root/.cache/ms-playwright
• /var/sandbox

4. Add playwright for pip install
5. Install necessary package for playwright
6. Run playwright install --with-deps chromium

✔️ Expected Behavior

Playwright should successfully launch Chromium (or other browsers) inside the sandbox, and correctly resolving and executing the bundled node binary from playwright/driver/node (ARM64)

❌ Actual Behavior

When trying to use Playwright in a Python Code node, launching the browser always fails with:

FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.10/site-packages/playwright/driver/node'

[dosubot]

This is a known limitation of the Dify sandbox, not a bug. The FileNotFoundError is caused by two independent sandbox security layers that both block Playwright:

1. Chroot isolation — The sandbox restricts the Python process's filesystem root to /var/sandbox/sandbox-python/. The python_lib_path config only bind-mounts .so shared libraries and Python modules for importing — it does not recursively expose all files under those paths. playwright/driver/node is a native ELF binary, not a Python module, so it's never mounted into the sandbox regardless of your python_lib_path settings [1].

2. seccomp syscall blocking — Even if the binary were accessible, Playwright needs to spawn a subprocess via execve, which is not in the sandbox's syscall allowlist. This allowlist is hardcoded in Go source code (syscalls_amd64.go) and cannot be changed via config.yaml — it requires rebuilding the sandbox image [2].

This was also reported in #21644 [3].

Workarounds:

• Rebuild the sandbox image — Follow the dify-sandbox FAQ workflow: use strace -c to capture required syscalls, add them (at minimum execve, wait4, clone, pipe2, etc.) to the allowlist in the Go source, also add playwright/driver to python_lib_path, then rebuild the Docker image [1].
• Use a community image — e.g., svcvit/dify-sandbox-py:0.1.2, which enables more syscalls by default.
• Call an external browser API (recommended for production) — Instead of running Playwright inside the Code node, call an external headless browser service (Browserless, Apify, etc.) over HTTP from your workflow. This sidesteps all sandbox constraints with no image changes needed.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[BBBChan]

@dosu.

I have already tried the three methods you mentioned:

1. After updating the syscalls allowlist and python_lib_path, then rebuilding the sandbox image, there is no more "operation not permitted" error. However, it still cannot find the playwright/driver/node file.
2. Using the community images svcvit/dify-sandbox-py:0.1.2 and svcvit/dify-sandbox-py:0.1.4, it still reports that the playwright/driver/node file cannot be found.
3. I created a new browserless/chrome container and modified the code to call browserless/chrome directly via Playwright, but it still throws the same error: cannot find playwright/driver/node file.

Would you have any other suggestions? Thank you.