Secret Volumes (With Demo) And Empty Volumes In Azure Container Cases

Secret Volumes 

  • Azure Container Cases help secret volumes and the key volumes permit you to retailer delicate knowledge. That delicate knowledge could possibly be your SSH keys or it could possibly be your database credentials.
  • One wonderful thing about that is that this knowledge is saved in a RAM-backed file system. So, there isn’t a concern of them being written to non-volatile storage.
  • On prime of that, Azure CLI helps the configuration of secret volumes with the assistance of two arguments.
  • The –secrets key=worth argument permits you to specify your secrets and techniques in a key=worth format.
  • The opposite argument which –secrets-mount-path /mnt/ktsecrets specifies whereby the container the secrets and techniques quantity needs to be mounted. Right here is my case, it could be mounted to ktsecrets.
  • Typically, one can find one file per secret in that path the place the file could be named after the key identify and the contents of the file could be the worth of the key. 

Allow us to go forward and see the demo for secret volumes the place we’ll see how simple it’s for our container to entry secrets and techniques saved in a secret quantity.

We’re going to retailer a single secret right into a quantity after which our container will entry the key.

  1. To begin with, login to your Azure account utilizing the az login command and choose your most well-liked subscription (when you have a couple of).


  2. Then, create a useful resource group and put it in your nearest datacenter.



  3. Now, we’ll create a container group and use the az container create command, specifying the container group and the useful resource group it’s in.


    We are going to use a really small Docker picture i.e. alpine Linux that may assist us to rapidly begin this up.


    The restart coverage could be set to by no means and we’re going to configure a secret that has the identify PASSWORD and the worth ‘A really huge secret!’


    We’re additionally going to mount the key on the /mnt/ketsecrets path. In that folder, there may be going to be a file with the identify PASSWORD and the content material ‘A really huge secret!’.


    To verify that this labored, we’re simply going to set a command line for our container to make use of cat to print out the contents of that file.



  4. In a real-time software, this secret would possibly comprise one thing like a database connection string and so your code would go and skim this file and use that when it is connecting to the database.


    As soon as we now have created the container, it will not take very lengthy to get operating as a result of the picture which we took could be very small and it’ll full in a short time.


  5. We are going to use the az container logs command to see what’s written to the log output. And we’d be capable of see the worth of our secret.



In a real-world situation, nevertheless, you, after all, will not write secrets and techniques right into a log file. This was only a demonstration of how simple it’s to make use of these secret volumes so you’ll be able to be sure that your secrets and techniques are by no means truly written to non-volatile storage.


Empty Volumes

  • You too can mount empty volumes in an Azure Container. It might sound just a little awkward to you and also you would possibly marvel why would you mount an empty quantity which isn’t truly backed by one thing like an Azure File Share.
  • However the factor is, an empty quantity may be accessed by any container inside a container group and so it permits them to have a approach of sharing recordsdata between them. It allows a sample of container utilization referred to as the sidecar sample.
  • A sidecar sample is one thing the place one container is used so as to add extra performance to a different.
  • Supposing that in our container group we now have obtained a container that’s anticipating to search out configuration saved in a YAML file in a selected location and one other container in the identical container group is aware of tips on how to name a configuration service that will get that configuration and creates the YAML file.
  • So, through the use of a shared empty quantity, one container can write into it and the opposite container can learn out of it.
  • You wouldn’t use an empty quantity to retailer precise software knowledge contents like a database as a result of it won’t dwell past the lifetime of your container group.

Nonetheless, there are some drawbacks of empty volumes,

  • Empty volumes are presently not supported by Azure CLI so it’s worthwhile to use ARM templates to create them.
  • They aren’t supported by Home windows Containers.
  • You possibly can go to the ACI documentation website right here to take a look at what are the present limitations of ACI.


  • As talked about above, Home windows does not help any of the quantity varieties and there are numerous quotas limiting issues like what number of container teams you’ll be able to have in your subscription and in addition how briskly you’ll be able to create them.
  • However one good factor is that you’ve the facility to request that these limits are elevated on your subscription as they’re just a little bit on the low facet at this second.
  • Nonetheless, these limits will develop into a bit extra beneficiant over time because the ACI companies are rising very quickly among the many customers.

Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button