Get Started

This page walks through running the localaz container and pointing the Azure CLI and SDKs at it.

Prerequisites

• Docker.
• The Azure CLI (az) and/or an Azure SDK, if you want to drive the emulator.

Run the container

Pull and run the published image from Docker Hub (linksociety/localaz), publishing each service port and mounting a volume for persistence:

docker run --name localaz \
  -p 10000:10000 -p 10001:10001 -p 10002:10002 \
  -p 10003:10003 -p 10004:10004 -p 10005:10005 \
  -p 10006:10006 -p 10007:10007 -p 5672:5672 \
  -v localaz-data:/data \
  linksociety/localaz:latest

The image is published for both linux/amd64 and linux/arm64 (the latter covers Apple Silicon / macOS arm64 hosts). State lives in /data, owned by the non-root user (uid 65532); the named localaz-data volume keeps it across restarts.

Stop and remove the container with:

docker rm -f localaz

Service endpoints

Once running, the services are available at:

Connect a client

The credentials match Azurite’s well-known development account, so existing tooling works unchanged. Because localaz uses Azurite’s default storage ports, the SDKs and CLI can connect with the UseDevelopmentStorage=true shorthand — no account name or key to write down or paste anywhere:

export AZURE_STORAGE_CONNECTION_STRING="UseDevelopmentStorage=true"

Both the Azure CLI and the SDKs pick up AZURE_STORAGE_CONNECTION_STRING automatically. A quick smoke test with the CLI:

az storage container create --name demo
az storage blob upload --container-name demo --name hello.txt --file ./hello.txt
az storage blob list --container-name demo -o table

The emulator accepts the Shared Key Authorization header (and Service Bus CBS tokens) but does not verify them.

See Services for per-service configuration flags, environment variables, and SDK/CLI examples.