azurite

packaged by Chainguard

Chainguard Container for azurite

Azurite is an open source Azure Storage API compatible server (emulator), providing Blob, Queue, and Table storage endpoints for local development and testing against the Azure Storage APIs.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/azurite:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard azurite image is compatible with the upstream Azurite. It emulates the Azure Storage Blob, Queue, and Table services and works with the official Azure Storage SDKs and tools (such as the Azure CLI and Azure Storage Explorer) via the well-known development storage account.

The image listens on the three default endpoints and binds them to 0.0.0.0 so they are reachable from outside the container:

• Blob service — port 10000
• Queue service — port 10001
• Table service — port 10002

Data is persisted under /data. Mount a volume at /data to retain state across container restarts.

Unlike the upstream image, which runs as root, this image runs as the non-root user nonroot (UID/GID 65532), and /data is owned by that user. A host directory bind-mounted at /data must be writable by UID 65532.

Storage API version

Like the upstream emulator, Azurite validates the x-ms-version header on each request and rejects versions newer than the release supports. Recent Azure Storage SDKs may negotiate a newer API version than this Azurite release recognizes, which surfaces as a version/authentication error. If you hit this, either pin your client to a supported API version, or start the container with --skipApiVersionCheck. Like the upstream image, this image runs docker-entrypoint.sh, which prepends node to any argument that is not an executable, so pass the full azurite command rather than the flag on its own, repeating the host bindings:

docker run -d -p 10000:10000 -p 10001:10001 -p 10002:10002 \
  cgr.dev/ORGANIZATION/azurite \
  azurite --location /data --blobHost 0.0.0.0 --queueHost 0.0.0.0 --tableHost 0.0.0.0 \
  --skipApiVersionCheck

Getting Started

To start Azurite with the default settings:

docker run -d -p 10000:10000 -p 10001:10001 -p 10002:10002 cgr.dev/ORGANIZATION/azurite

To persist data on the host, mount a volume at /data:

docker run -d -p 10000:10000 -p 10001:10001 -p 10002:10002 \
  -v "$(pwd)/azurite-data:/data" cgr.dev/ORGANIZATION/azurite

Connect using the well-known development connection string:

UseDevelopmentStorage=true

Documentation and Resources

• Azurite Official Documentation
• Azurite GitHub Repository
• Chainguard Images Migration Guide

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.