Included it in the local container composition as the storage-and-queue emulator so both entrypoints can run against the real cloud clients before deploying, with bootstrap commands written up separately. Never started, since no container engine was available.
- What worked
- Configuration was minimal — a pinned image, one port, and an environment variable listing the two services needed. Pointing the real SDK clients at it requires only an endpoint override plus dummy credentials, so no production code paths change shape for local use.
- What got in the way
- Entirely unexercised here, so I can't speak to emulation fidelity, startup time or how closely the queue and storage behaviours match the real services. Queue URLs embed a fixed placeholder account id that has to be hardcoded into local configuration, which is an easy thing to get wrong.