Describe the bug
Volume mount 'default-token-*' referenced in Bridge To Kubernetes config file 'KubernetesLocalProcessConfig.yaml' does not exist in the remote container
To Reproduce
Run the connection B2K using a KubernetesLocalProcessConfig.yaml defining a volumesMount
**Expected behavior**
A clear and concise description of what you expected to happen.
**Logs**
Attach logs from the following directory:
For Windows: %TEMP%/Bridge to Kubernetes
For OSX/Linux: $TMPDIR/Bridge to Kubernetes
If you are a Visual Studio user,
- Set the environment variable MS_VS_AZUREDEVSPACES_TOOLS_LOGGING_ENABLED=true
- Open Visual Studio and run your scenario
- Provide logs from: %temp%\Microsoft.VisualStudio.Kubernetes.Debugging
**Environment Details**
Client used (VS Code/Visual Studio):
mindaro-dev.file-downloader@1.0.11
mindaro.mindaro@1.0.120210803
1.62.2
3a6960b964327f0e3882ce18fcebd07ed191b316
x64
Client's version:
Operating System:
linux manjaro
**Additional context**
Add any other outputs from the clients or context you would like to share.
Describe the bug Volume mount 'default-token-*' referenced in Bridge To Kubernetes config file 'KubernetesLocalProcessConfig.yaml' does not exist in the remote container
version: 0.1 volumeMounts:
To Reproduce Run the connection B2K using a KubernetesLocalProcessConfig.yaml defining a volumesMount
**Expected behavior** A clear and concise description of what you expected to happen. **Logs** Attach logs from the following directory: For Windows: %TEMP%/Bridge to Kubernetes For OSX/Linux: $TMPDIR/Bridge to Kubernetes If you are a Visual Studio user, - Set the environment variable MS_VS_AZUREDEVSPACES_TOOLS_LOGGING_ENABLED=true - Open Visual Studio and run your scenario - Provide logs from: %temp%\Microsoft.VisualStudio.Kubernetes.Debugging **Environment Details** Client used (VS Code/Visual Studio): mindaro-dev.file-downloader@1.0.11 mindaro.mindaro@1.0.120210803 1.62.2 3a6960b964327f0e3882ce18fcebd07ed191b316 x64 Client's version: Operating System: linux manjaro **Additional context** Add any other outputs from the clients or context you would like to share.