不同 Synology 型号和 DSM 内核能力并不一致。某些设备可能出现:
- CPU CFS quota 不可用,设置
cpus或 NanoCPUs 会导致容器创建失败; - PID cgroup 不可用,
pids_limit被忽略并产生警告; - Chromium sandbox 所需的 user namespace 或 seccomp 能力不完整。
建议:
- 先只使用
mem_limit; - 通过
SEARCH_MAX_CONCURRENCY、EXTRACT_MAX_CONCURRENCY和BROWSER_MAX_CONCURRENCY控制应用并发; - Chromium 默认并发设为 1;
- 在确认设备能力前保持
BROWSER_SANDBOX=false; - 不要为了启动 Chromium 添加
SYS_ADMIN; - 使用 Docker 网络层或宿主防火墙阻止 extractor 访问 NAS 管理网段。
这些是兼容性建议,不代表所有 DSM 设备都缺少相关 cgroup 能力。
Kernel capabilities vary across Synology models and DSM releases. Some systems may exhibit:
- unavailable CPU CFS quota, causing
cpusor NanoCPUs settings to fail container creation; - unavailable PID cgroups, causing
pids_limitto be ignored; - incomplete user-namespace or seccomp support required by Chromium sandboxing.
Recommendations:
- start with
mem_limitonly; - control load through
SEARCH_MAX_CONCURRENCY,EXTRACT_MAX_CONCURRENCY, andBROWSER_MAX_CONCURRENCY; - keep browser concurrency at 1;
- leave
BROWSER_SANDBOX=falseuntil host support is verified; - do not add
SYS_ADMINmerely to make Chromium start; - block access to NAS management networks at the Docker or host firewall layer.
These are compatibility notes and do not imply that every DSM system lacks the corresponding cgroup features.