zeroclaw-labs/zeroclaw · error · anyhow::Error
Failed to recursively change ownership of
Error message
Failed to recursively change ownership of {} to zeroclaw:zeroclaw: {} What it means
The recursive `chown -R zeroclaw:zeroclaw <path>` step of service installation returned non-zero with stderr embedded. Applied to directories like the data/log roots; fails on unreadable entries, filesystems that reject ownership changes, or a missing user/group.
Solutions
- Run with sudo and check the recursive chown error detail for the path.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at crates/zeroclaw-runtime/src/service/mod.rs:1568 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zeroclaw-labs/zeroclaw@88bb9c8533 (2026-08-23).
Data as JSON: /api/errors/ad402cd384d5e850.
Report an issue: GitHub.
Appendix: source
Thrown at crates/zeroclaw-runtime/src/service/mod.rs:1568
}
Ok(())
}
#[cfg(not(unix))]
fn chown_to_zeroclaw(_path: &Path) -> Result<()> {
Ok(())
}
#[cfg(unix)]
fn chown_recursive_to_zeroclaw(path: &Path) -> Result<()> {
let output = Command::new("chown")
.args(["-R", "zeroclaw:zeroclaw", &path.to_string_lossy()])
.output()
.context("Failed to run recursive chown")?;
if !output.status.success() {
let stderr = String::from_utf8_lossy(&output.stderr);
bail!(
"Failed to recursively change ownership of {} to zeroclaw:zeroclaw: {}",
path.display().to_string(),
stderr.trim(),
);
}
Ok(())
}
#[cfg(not(unix))]
fn chown_recursive_to_zeroclaw(_path: &Path) -> Result<()> {
Ok(())
}
fn copy_dir_recursive(source: &Path, target: &Path) -> Result<()> {
fs::create_dir_all(target).with_context(|| {
format!(
"Failed to create directory {}",View on GitHub (pinned to 88bb9c8533)