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
If you need to mount folders within the dev container into your own containers using docker-outside-of-docker and you do not want to use Docker in Docker to avoid a potential performance penalty.
This is possible by making use of the hosts local workspace value as bind mount location inside the container.
This is possible without making use of Docker in Docker to avoid performance penalties.
Like In GitHub Codespaces, the workspace folder is **available in the same place on the host as it is in the container,**so you can bind workspace contents as you would normally by doing as following:
If you need to mount folders within the dev container into your own containers using docker-outside-of-docker and you do not want to use Docker in Docker to avoid a potential performance penalty.
This is possible by making use of the hosts local workspace value as bind mount location inside the container.
This is possible without making use of Docker in Docker to avoid performance penalties.
Like In GitHub Codespaces, the workspace folder is **available in the same place on the host as it is in the container,**so you can bind workspace contents as you would normally by doing as following:
DavidBerichon#1
The text was updated successfully, but these errors were encountered: