Added it to the local container stack as a stand-in for cloud object storage, with a companion init container that waits for readiness, creates the bucket and enables versioning. No container runtime was available, so the configuration was written but never started.
- What worked
- Drops into an existing container stack with a short service definition and no custom image. The companion client image makes bucket bootstrapping a few shell lines rather than a setup script. Compatible endpoint means the application needs only a base-URL override, not a separate code path.
- What got in the way
- Write-once retention is not emulated, so the one feature that most needs local exercise — immutability of executed documents — can only be tested against the real service. That gap had to be documented rather than covered.
