Blobfuse command

Question

Can we connect azure blob storage without config file? I'm using below command to mount the azure blob container, That was working fine. Due to some security reasons we don't like to mention container name that was mounting multiple mounts on single container also account keys are visible to users. So tried without giving container details in config file and tried to mount with in the command that doesn't work and throwing error. Kindly give us solution.

Command:

blobfuse "$mount_point" --tmp-path=/mnt/resource/blobfusetmp --config-file=/fuse_file.cfg -o attr_timeout=240 -o entry_timeout=240 -o negative_timeout=120 -o allow_other --container-name="$container" --log-level=LOG_DEBUG --file-cache-timeout-in-seconds=120

Config file

[root@exxxxxx1 /]# cat fuse_connection.cfg

accountName xxxxxx

accountKey xxxxxxx

containername xyz

authType Key

Answer 1

Hi @goutham varma

Greetings! Thanks for using Microsoft Q&A Forum and posting your query here!

Yes, you can connect to Azure Blob Storage without a configuration file by specifying the necessary parameters directly in the command line. However, please make sure that you provide all required parameters, including the account name and key, along with the container name.

If you want to avoid exposing the container name in the config file, you can specify it directly in the command. Here's an example of how this:

blobfuse "$mount_point" --tmp-path=/mnt/resource/blobfusetmp --account-name=<your_account_name> --account-key=<your_account_key> --container-name=<your_container_name> -o attr_timeout=240 -o entry_timeout=240 -o negative_timeout=120 -o allow_other --log-level=LOG_DEBUG --file-cache-timeout-in-seconds=120

Make sure to replace <your_account_name>, <your_account_key>, and <your_container_name> with your actual Azure Blob Storage account name, key, and container name.

If you want to avoid exposing the account key, consider using a more secure authentication method, such as a Shared Access Signature (SAS) or Managed Identity, if applicable.

By passing the container name as a parameter in the command line, you can avoid mentioning the container name in the config file. This will also prevent multiple mounts on a single container.

Additional information: This is can also due to a missing dependency on the system. Kindly run below command and then try mount again.

sudo yum install git cmake fuse-devel libcurl-devel gcc gcc-c++ gnutls-devel libgcrypt-devel libuuid-devel fuse -y

If the issue still persists, can you please share the below mentioned details for future troubleshooting:

• What version of blobfuse are they using?
• Which OS (and OS version) are they using?
• Share the screenshot of the error message?

For more information, please refer the below documents:

• How to mount Azure Blob Storage as a file system with BlobFuse v1
• How to use the BlobFuse2 mount command

Hope this helps!

Kindly let us know if the above helps or you need further assistance on this issue.

---

Please don’t forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.