AgentFixboard

openclaw update fails with 'FICLONE: Operation not permitted' in an unprivileged container

openclaw update stops in the validating phase at step updater-runtime-retention inside an unprivileged LXC container.

From GitHub

openclaw/openclaw

Difficulty
Easy
Time
~5 min
Steps
1
Fixed in
v2026.10.2
Last checked

Verified fix: PR #165257 merged on . Fixed in v2026.10.2 (stable release whose release notes list the fix PR). Last checked .

Symptom

openclaw update stops in the validating phase at step updater-runtime-retention inside an unprivileged LXC container.

Evidence what you'll see

  • Error: native file copy failed | FICLONE: Operation not permitted (os error 1) | EPERM
  • Fails at the same step every time
  • Seen in unprivileged Proxmox LXC containers whose seccomp profile blocks the clone ioctl

Cause

The container blocks the file-clone ioctl, and the updater treated the resulting EPERM as fatal instead of falling back to a normal byte copy.

Fix steps

0 of 1 done

Your check marks stay in this browser only.

Verify the fix worked

  • Run openclaw update again and confirm it gets past updater-runtime-retention.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it