You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried with the latest version of Docker Desktop
I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID:
Expected behavior
When creating a new docker dev environment, I can choose one of the sources:
Exsiting Git repo (using Volume)
Local directory (using Bind-Mount)
Either of them will create a folder under ~/.docker/devenvironments, with a file devenv.log.
When I select Local directory, it works as expected: default compose-dev.yaml file was created under my directory. I can connect to the container in vscode, and edit the file to change the image to my customized image. After deleting and restarting the container, it takes effect.
However, when I choose "Exsiting Git repo", it behaves different out of my expectation. I cannot change the image this way (edit the file in vscode).
Actual behavior
From my observation, to modify compose-dev.yaml file in the volume by vscode has no effect. But it's useful if I modify ~/.docker/devenvironments/[devenv-name]/repository/compose-dev.yaml file in macOS.
My question:
Why is there ~/.docker/devenvironments/[devenv-name]/repository directory? This copy seems to be useless because the git repository will be cloned to the docker volume as well (which can be accessed by vscode).
On the contrary, why ~/.docker/devenvironments/[devenv-name]/repository/compose-dev.yaml take effect but not the file under the docker volume? It's very obscure and inconvenient. So what is the best way to modify the compose-dev.yaml file?
Information
macOS Version: 13.1 (22C65)
Intel chip or Apple chip: M1 Pro
Docker Desktop Version: 4.16.2 (95914)
Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Steps to reproduce the behavior
...
...
The text was updated successfully, but these errors were encountered:
Thanks for the report. Dev Environments is still a beta feature with some rough edges here and there. This is good feedback and we'll discuss in the team how to improve these local folders.
Expected behavior
When creating a new docker dev environment, I can choose one of the sources:
Either of them will create a folder under
~/.docker/devenvironments
, with a filedevenv.log
.When I select Local directory, it works as expected: default
compose-dev.yaml
file was created under my directory. I can connect to the container in vscode, and edit the file to change the image to my customized image. After deleting and restarting the container, it takes effect.However, when I choose "Exsiting Git repo", it behaves different out of my expectation. I cannot change the image this way (edit the file in vscode).
Actual behavior
From my observation, to modify
compose-dev.yaml
file in the volume by vscode has no effect. But it's useful if I modify~/.docker/devenvironments/[devenv-name]/repository/compose-dev.yaml
file in macOS.My question:
~/.docker/devenvironments/[devenv-name]/repository
directory? This copy seems to be useless because the git repository will be cloned to the docker volume as well (which can be accessed by vscode).~/.docker/devenvironments/[devenv-name]/repository/compose-dev.yaml
take effect but not the file under the docker volume? It's very obscure and inconvenient. So what is the best way to modify thecompose-dev.yaml
file?Information
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: