How to configure settings for BlobFuse2
You can use configuration settings to manage BlobFuse2 in your deployment. Through configuration settings, you can set these aspects of how BlobFuse2 works in your environment:
- Access to a storage blob
- Pipeline engagement
- Caching behavior
For a list of all BlobFuse2 settings and their descriptions, see the base configuration file on GitHub.
To manage configuration settings for BlobFuse2, you have three options (in order of precedence):
Using a configuration file is the preferred method, but the other methods might be useful in some circumstances.
Creating a configuration file is the preferred method to establish settings for BlobFuse2. When you've specified the settings you want in the configuration file, reference the configuration file when you use
blobfuse2 mount or other commands.
Here's an example:
blobfuse2 mount ./mount --config-file=./config.yaml
The BlobFuse2 base configuration file contains a list of all settings and a brief explanation of each setting.
Setting environment variables is another way to configure some BlobFuse2 settings. The supported environment variables are useful for specifying the Azure Blob Storage container to access and the authorization method to use.
For more information about using environment variables and a list of all variables you can use, see the BlobFuse2 README.
You also can set configuration settings when you pass them as parameters of the BlobFuse2 command set, such as by using the
blobfuse2 mount command. The mount command typically references a configuration file that contains all the settings. But you can use CLI parameters to override individual settings in the configuration file. In this example, the config.yaml configuration file is referenced, but the container to be mounted and the logging options are overridden:
blobfuse2 mount ./mount_dir --config-file=./config.yaml --container-name=blobfuse2b --log-level=log_debug --log-file-path=./bobfuse2b.log