azure-blob-storage
Azure Blob Storage
docker pull mcr.microsoft.com/azure-blob-storage
Azure Blob Storage on IoT Edge provides block and append blob storage solution at the edge. A blob storage module on your IoT Edge device behaves like an Azure blob service, but the block blobs or append blobs are stored locally on your IoT Edge device. You can access your blobs using the same Azure storage SDK methods or blob API calls that you're already used to. For more information checkout Azure Blob Storage on IoT Edge
See the Deploy Azure Blob Storage on IoT Edge documentation.
See the Deploy Azure Blob Storage on IoT Edge documentation.
You can retrieve a list of all available tags for azure-blob-storage at https://mcr.microsoft.com/v2/azure-blob-storage/tags/list
If you have any problems with or questions about this image, please contact us through a GitHub issue.
Please provide feedback to Feedback.
Database\lost directory inside the module volume. If the module experiences frequent power loss it may be necessary to clean the lost directory to free up the storage space. If the repair process is not successful, the module won't startup. Please create a new volume for the storage module or delete all files from the current volume to allow the module to start.| Field | Possible Values | Explanation |
|---|---|---|
| tieringOn | true, false | By default it is set to false, if you want to turn it On set it to true |
| backlogPolicy | NewestFirst, OldestFirst | Allows you to choose the order in which the data is copied to Azure. By default it is set to OldestFirst. The order is determined by last modified time of Blob |
| remoteStorageConnectionString | "DefaultEndpointsProtocol=https;AccountName=<your Azure Storage Account Name>;AccountKey=<your Azure Storage Account Key>;EndpointSuffix=<your end point suffix>" is a connection string that allows you to specify the Azure Storage account to which you want your data uploaded. Specify Azure Storage Account Name, Azure Storage Account Key, End point suffix. Add appropriate EndpointSuffix of Azure where data will be uploaded, it varies for Global Azure, Government Azure, and Microsoft Azure Stack. | |
| tieredContainers | "<source container name1>": {"target": "<target container name>"},"<source container name1>": {"target": "%h-%d-%m-%c"}, "<source container name1>": {"target": "%d-%c"} | Allows you to Specify the container names you want to upload to Azure. This module allows you to specify both source and target container names. If you don't specify the target container name, it will automatically assign the container name as <IoTHubName>-<IotEdgeDeviceName>-<ModuleName>-<ContainerName>. You can create template strings for target container name, check out the possible values column. * %h -> IoT Hub Name (3-50 characters). * %d -> IoT device ID (1 to 129 characters). * %m -> Module Name (1 to 64 characters). * %c -> Source Container Name (3 to 63 characters). Maximum size of the container name is 63 characters, while automatically assigning the target container name if the size of container exceeds 63 characters it will trim each section (IoTHubName, IotEdgeDeviceName, ModuleName, ContainerName) to 15 characters. |
| Field | Possible Values | Explanation |
|---|---|---|
| ttlOn | true, false | By default it is set to false, if you want to turn it On set it to true |
| timeToLiveInMinutes | <minutes> | Specify the TTL in minutes. The module will automatically delete your blobs from local storage when TTL expires |
No tags have been pushed to this repository yet.