zerobyte icon indicating copy to clipboard operation
zerobyte copied to clipboard

ZeroByte cannot detect rclone remotes - "Failed to spawn process: EACCES"

Open peyloride opened this issue 1 week ago • 1 comments

ZeroByte fails to list rclone remotes with the error:

bun: Failed to spawn process: EACCES
error > Failed to list rclone remotes: bun: Failed to spawn process: EACCES

The rclone binary and config are accessible when tested directly via docker exec, but the app itself cannot spawn rclone processes.

Environment

  • ZeroByte v0.18
  • Host: Proxmox VE (Linux 6.14.11-4-pve)
  • Container: Alpine 3.22
  • Bun v1.3.3

Root Cause

This is a Bun runtime issue where Docker's default seccomp/apparmor profiles block syscalls that Bun uses internally when spawning child processes.

Related Bun issue: https://github.com/oven-sh/bun/issues/15616

Workaround

Add these security options to docker-compose.yml:

cap_add:
  - SYS_ADMIN # Already there
  - SYS_PTRACE
security_opt:
  - seccomp:unconfined
  - apparmor:unconfined

I'm not expert at security but just wanted to flag that these options are working and I think it's much better than having a privileged container.

peyloride avatar Dec 15 '25 18:12 peyloride