A lightweight server clone of Azure Blob, Queue, and Table Storage that simulates most of the commands supported by it with minimal dependencies.
In order to run Azurite you need Node.js >= 6.0 installed on your system. Azurite works cross-platform on Windows, Linux, and OS X.
After installation you can install Azurite simply with
npm which is Node.js package management tool and which is included with every Node.js installation.
$ npm install -g azurite
Then simply start it with the following command:
$ azurite -l path/to/localfolder
This tells Azurite to store all data in a particular directory. If the
-l option is ommitted it will use the current working directory. This also will start both blob storage and queue storage emulation in two different processes.
You can also selectively start the different storage emulators.
For Blob Storage Emulator only:
$ azurite-blob -l path/to/azurite/workspace
For Queue Storage Emulator only:
For Table Storage Emulator only:
$ azurite-table -l path/to/azurite/workspace
PM> Install-Package Azurite
This will install Azurite to your current project and also immediately start it in a dedicated console window. Note that you do not need to install Node.js since Azurite is packaged into a single self-contained executable, thanks to pkg.
Every release of Azurite starting with version 0.9.7 is available at Docker Hub and ready to be pulled with:
$ docker pull arafato/azurite
Please note that the
latest tag will always refer to the latest release.
To build the Docker image yourself, execute the following:
$ docker build -t arafato/azurite .
To run the Docker image, execute the following command:
$ docker run -d -t -p 10000:10000 -p 10001:10001 -v /path/to/folder:/opt/azurite/folder arafato/azurite
By default, the container starts all services available (currently blob, queue, and table).
Using the environment variable
executable, specific executables can be specifed:
blobStart the Blob Storage Emulator only
queueStart the Azure Queue Storage Emulator only
tableStart the Azure Table Storage Emulator only
$ docker run -e executable=blob -d -t -p 10000:10000 -v /path/to/folder:/opt/azurite/folder arafato/azurite
To perform blob storage operations using the 2.0 Azure cross-platform CLI, you need to operate with the appropriate connection string. The values within are based on the hardcoded Azure Storage Emulator values.
Example command to create a container:
$ az storage container create --name 'test' --connection-string 'DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=;'
If you are interested in making a code contribution and would like to learn more about the technologies that we use, check out the list below.
The current status of Azurite's support of the Official Blob Storage REST API Specification is listed in below section API Support. Features that are still unimplemented are marked with
[TODO]. Features that are currently being worked on are marked with
Current bugs that need to be fixed are listed at our issues site on Github and tagged with a red label
Never made an open source contribution before? Wondering how contributions work in Azurite? Here's a quick rundown!
Find an issue that you are interested in addressing or a feature that you would like to add.
Fork the Azurite repository to your local GitHub organization. This means that you will have a copy of the repository under
Clone the repository to your local machine using git clone
Create a new branch for your fix using
git checkout -b branch-name-here.
Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
git add insert-paths-of-changed-files-here to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.
Push the changes to the remote repository using
git push origin branch-name-here.
Submit a pull request to the upstream repository. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352". In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
Wait for the pull request to be reviewed by a maintainer. Make changes to the pull request if the reviewing maintainer recommends them.
Celebrate your success after your pull request is merged!
If you need help, you can ask questions directly at our issues site on Github.
The Standard Emulator Connection String is the same as required by Microsoft's Official Storage Emulator:
All DONE except:
Account SAS Support [TODO]
See https://docs.microsoft.com/en-us/rest/api/storageservices/constructing-an-account-sas for specification
Get Blob Service Stats [TODO]
Retrieves statistics related to replication for the Blob service. This operation is only available on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account.
Set Blob Tier [TODO] The Set Blob Tier operation sets the tier on a blob.
ALL DONE except: