This commit is contained in:
@@ -122,3 +122,22 @@ if problems building, execute `DOCKER_BUILDKIT=0` with.
|
|||||||
``` bash
|
``` bash
|
||||||
DOCKER_BUILDKIT=0 docker build --pull --rm -f 'podman/ubuntu-fatboy.Dockerfile' -t 'podman-dev:latest' 'podman'
|
DOCKER_BUILDKIT=0 docker build --pull --rm -f 'podman/ubuntu-fatboy.Dockerfile' -t 'podman-dev:latest' 'podman'
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## docker outside docker
|
||||||
|
|
||||||
|
```json
|
||||||
|
....
|
||||||
|
"features": {
|
||||||
|
"ghcr.io/devcontainers/features/docker-outside-of-docker": {},
|
||||||
|
},
|
||||||
|
// mount the workspace using the same absolute path on both the host and the devcontainer.
|
||||||
|
// This is required because we use Docker-Outside-of-Docker (DooD). In DooD setups, the Docker
|
||||||
|
// daemon runs on the host and cannot see the devcontainer filesystem. If the paths differ,
|
||||||
|
// bind mounts in docker-compose will fail: the daemon won't find the source path and will
|
||||||
|
// create empty directories instead of mounting files. Using workspaceMount + workspaceFolder
|
||||||
|
// ensures the host and the devcontainer share the exact same path, making volume mounts work
|
||||||
|
// reliably for all developers.
|
||||||
|
"workspaceMount": "source=${localWorkspaceFolder},target=${localWorkspaceFolder},type=bind",
|
||||||
|
"workspaceFolder": "${localWorkspaceFolder}",
|
||||||
|
...
|
||||||
|
```
|
||||||
|
|||||||
Reference in New Issue
Block a user