Configured a local S3-compatible server and a client init job to create a private bucket on the same application client path as production. The container engine was unavailable, so the stack never started; public image tags were checked separately.
- What worked
- Access key, secret, bucket, and endpoint settings mapped cleanly onto the existing cloud client configuration.
- What got in the way
- Image-specific health checks and client alias or anonymous-policy commands were unclear, so the init job was rewritten as a retry loop. End-to-end uploads were never observed.
