Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
I mounted an Azure blob in my Linux system via blobfuse2. After that, I can see the content of the Azure blobstorage in my local workspace. But when I start the devcontainer in that workspace, the content of the blobfuse disappears. The only way to get the blobfuse content in the devcontainer is to rebuild the container. Similarly, if I unmount the blobfuse in the host, the content will still be visible in the devcontainer until a rebuilt. In summary, the devcontainer does not map (nor update) a blobfuse mount correctly.
It used to work few months ago, but I cannot remember what version of vscode/blobfuse I used. Since then, there have been few updates.
Steps to Reproduce:
Mount a blobstorage with blobfuse2 in the workspace blobfuse2 mount <...> --config-file=<...> where the config file is something like
azstorage:
type: block
account-name: <...>
container: <...>
mode: sas
2. Start the devcontainer in that workspace
3. All folders in the workspace will be mounted correctly, but the blobfuse one will not be updated correctly.
<!-- Check to see if the problem is general, with a specific extension, or only happens when remote -->
Does this issue occur when you try this locally?: No, the blobfuse folder is mounted correctly
Does this issue occur when you try this locally and all extensions are disabled?: No
<!-- If your issue only appears in Codespaces, please visit: https://github.com/github/feedback/discussions/categories/codespaces-feedback -->
Related to issue https://github.com/Azure/azure-storage-fuse/issues/1522
I tried with a vanilla docker container (no custom settings, no VSCode) and I see the same behavior. I think this is related to Docker and/or Blobfuse2 rather than VSCode. Closing for now
I mounted an Azure blob in my Linux system via blobfuse2. After that, I can see the content of the Azure blobstorage in my local workspace. But when I start the devcontainer in that workspace, the content of the blobfuse disappears. The only way to get the blobfuse content in the devcontainer is to rebuild the container. Similarly, if I unmount the blobfuse in the host, the content will still be visible in the devcontainer until a rebuilt. In summary, the devcontainer does not map (nor update) a blobfuse mount correctly.
It used to work few months ago, but I cannot remember what version of vscode/blobfuse I used. Since then, there have been few updates.
Steps to Reproduce:
blobfuse2 mount <...> --config-file=<...>
where the config file is something likelogging: type: syslog level: log_debug
components:
libfuse: attribute-expiration-sec: 120 entry-expiration-sec: 120 negative-entry-expiration-sec: 240
file_cache: path:
timeout-sec: 120
max-size-mb: 4096
attr_cache: timeout-sec: 7200
azstorage: type: block account-name: <...> container: <...> mode: sas