Update README.md
This commit is contained in:
Родитель
21e95dd377
Коммит
31ccd00292
|
@ -4,14 +4,14 @@
|
|||
|
||||
*Illustrates how you can use it to access your local Docker install from inside the a dev container by simply volume mounting the Docker unix socket. This variation uses `runArgs` and a `Dockerfile` to do the volume mounting*
|
||||
|
||||
> **Note:** You can also check out the [Docker Compose](../docker-in-docker-compose) variation of this same definition.
|
||||
|
||||
| Metadata | Value |
|
||||
|----------|-------|
|
||||
| *Contributors* | The VS Code team |
|
||||
| *Definition type* | Dockerfile |
|
||||
| *Languages, platforms* | Any |
|
||||
|
||||
> **Note:** There is also a [Docker Compose](../docker-in-docker-compose) variation of this same definition.
|
||||
|
||||
## Description
|
||||
|
||||
Dev containers can be useful for all types of applications including those that also deploy into a container based-environment. While you can directly build and run the application inside the dev container you create, you may also want to test it by deploying a built container image into your local Docker Desktop instance without affecting your dev container. This example illustrates how you can do this by running CLI commands and using the [Docker VS Code extension](https://marketplace.visualstudio.com/items?itemName=PeterJausovec.vscode-docker) right from inside your dev container.
|
||||
|
@ -44,4 +44,4 @@ The trick that makes this work is as follows:
|
|||
"runArgs": ["-v","/var/run/docker.sock:/var/run/docker.sock"]
|
||||
```
|
||||
|
||||
That's it!
|
||||
That's it!
|
||||
|
|
Загрузка…
Ссылка в новой задаче