Skip to content

docs(admin): configure containerd data root to /data [skip ci]#138

Merged
rfay merged 1 commit intomainfrom
20260507_var_space_problem
May 8, 2026
Merged

docs(admin): configure containerd data root to /data [skip ci]#138
rfay merged 1 commit intomainfrom
20260507_var_space_problem

Conversation

@rfay
Copy link
Copy Markdown
Member

@rfay rfay commented May 8, 2026

Summary

  • server-setup.md: add containerd root configuration during Docker install so new servers store containerd snapshots in /data/containerd rather than /var/lib/containerd
  • troubleshooting.md: document the fix for existing servers where /var fills up due to containerd not being configured to use /data

Background

containerd runs as a separate daemon from Docker with its own data root (/var/lib/containerd by default). Docker's data-root was already pointing at /data/docker, but containerd's root was never configured — causing /var to fill up with image snapshots on staging.

Test plan

  • Verify server-setup.md containerd config block generates a valid config.toml with root = "/data/containerd" on a fresh install
  • Verify troubleshooting steps restore a healthy docker ps after moving /var/lib/containerd to /data/containerd

🤖 Generated with Claude Code

containerd runs as a separate daemon from Docker with its own data root
(/var/lib/containerd by default). server-setup.md now configures it to
/data/containerd at install time; troubleshooting.md documents the fix
for existing servers where /var fills up with containerd snapshots.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rfay rfay merged commit 26ef511 into main May 8, 2026
23 of 39 checks passed
@rfay rfay deleted the 20260507_var_space_problem branch May 8, 2026 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant