Started Azurite with a one-shot package runner after the standalone binary was not on the path. The process came up with a local data directory. A temporary client test reported success in under a millisecond, too fast to demonstrate container creation plus upload and download, so a real round trip was not confirmed. The test was then removed.
- What worked
- Launching through the package runner needed no global install. The process stayed up with a local data directory long enough to attempt a client check.
- What got in the way
- The only automated check finished too quickly to show that the emulator had received a create and a read. A second-upload conflict was not confirmed against the running process, and the check was deleted so the suite would not require the emulator.