20 lines
1.7 KiB
Markdown
20 lines
1.7 KiB
Markdown
# 06 — Control the Docker daemon Target
|
|
|
|
**What to build:** A systemd-managed Docker daemon Target that configures daemon network proxying separately from container defaults and performs an explicit, confirmed restart with truthful post-operation state.
|
|
|
|
**Blocked by:** 02 — Safely control the Shell Target.
|
|
|
|
**Status:** in-progress
|
|
|
|
- [ ] The Target is Available only when a supported systemd-managed Docker daemon is detected.
|
|
- [ ] The explanation states that it affects daemon operations such as registry access, not container network traffic or container/build defaults.
|
|
- [ ] Pressing Space presents a restart warning before any configuration mutation.
|
|
- [ ] Cancelling the warning performs no file write, manager reload, or daemon restart.
|
|
- [ ] Confirming applies the compatible Active Profile through a managed daemon configuration surface, reloads manager configuration as required, and immediately restarts Docker.
|
|
- [ ] There is no Pending Restart state; success is reported only after restart and post-operation inspection succeed.
|
|
- [ ] Failure to write, reload, or restart produces immediate redacted feedback and re-inspects actual configuration as Enabled, Disabled, External, or Drifted.
|
|
- [ ] Existing recognized daemon proxy configuration is preserved and restored when the managed Target is disabled.
|
|
- [ ] Unsupported protocol or Bypass data rejects the operation before mutation rather than being omitted.
|
|
- [ ] Missing authority is reported as a normal permission error; the Adapter never initiates privilege escalation.
|
|
- [ ] Adapter contract and Target-specific tests fake systemd and Docker behavior and prove cancellation, command ordering, restart failure, restoration, and idempotency without touching the host daemon.
|