Note: The D:\Projects\Git\NuGetTypeSearch\.idea\azurite path was added into. In the below screenshot, you can see I mapped D:\Projects\Git\NuGetTypeSearch\.idea\azurite to /data in the container. Since we want to preserve the Azurite data locally with our solution, we can create a bind mount as well.
We’ll also have to specify the port bindings (port 1001). Optionally, we can name the container (I picked azurite here). In Rider, we can create a new Run Configuration ( Run | Edit Configurations), of the type Docker Image, and enter the image ID as /azure-storage/azurite. Setting up an Azurite run configuration in Rider When working on different projects and solution, this is great! For every solution, we can map a different path, and preserve the blobs and queues related to that solution in Azurite. This means that we can map /data to a folder on our host machine. Inside the Docker container, Azurite uses the /data folder to store blobs and queue messages. This will fetch and run the /azure-storage/azurite image, exposing ports 10000 (blob) and 10001 (queue). We can run Azurite using Docker, by running the following command:ĭocker run -p 10000:10000 -p 10001:10001 /azure-storage/azurite Different solution? Different path! The blobs and queues related to that solution in Azurite.
#How to use azure storage emulator on a mac how to#
In this blog post, we’ll see how we can use Azurite, an open source Azure Storage API compatible server (emulator), in Docker, and how to run it from JetBrains Rider. Run Azurite in Docker with Rider and keep Azure Storage data local to a solution JEdit on GitHub
0 kommentar(er)
