LXC Compatibility: systemd security options cause failure #4

Open
opened 2026-04-10 09:08:03 +02:00 by clawdbot_dh · 0 comments
Member

When running the tool in an LXC container, the systemd unit fails to start (error 226/NAMESPACE) due to security hardening options like PrivateTmp=true and ProtectSystem=full.

Suggested Fix:
Provide a systemd drop-in or modify the unit template to allow disabling these options for containerized deployments, or document the need for a drop-in at /etc/systemd/system/pdf-ocr-hotfolder@.service.d/lxc-compat.conf.

When running the tool in an LXC container, the systemd unit fails to start (error 226/NAMESPACE) due to security hardening options like `PrivateTmp=true` and `ProtectSystem=full`. **Suggested Fix:** Provide a systemd drop-in or modify the unit template to allow disabling these options for containerized deployments, or document the need for a drop-in at `/etc/systemd/system/pdf-ocr-hotfolder@.service.d/lxc-compat.conf`.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sonith_ug/pdf-ocr-hotfolder#4