Skip to content

Templatize the docker-prune systemd unit for multi-host use #4894

Description

@JSONbored

Problem: The example systemd unit for periodic Docker pruning hardcodes a single working directory — one unit serves exactly one host today.

Area: ORB / Fleet ops

Proposal: Convert it to a templated unit (@.service) parameterized by instance, so it can be reused across a fleet without hand-editing per host.

Deliverables:

  • A templated systemd unit usable across multiple hosts.

AMS Cloud Readiness cross-reference (added 2026-07-12)

See also #5220, #5222 in the new AMS Cloud Readiness milestone (#28) — the AMS-side parallel to this exact problem, already citing this issue as precedent. Keep both sides in sync if either design changes.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions