From 8b4242797b166488ddb052c7a8a218b239da494a Mon Sep 17 00:00:00 2001
From: "marcio.fernandes" <2+marcio.fernandes@noreply.localhost>
Date: Mon, 20 Jul 2026 15:12:35 +0000
Subject: [PATCH] Update README.md

---
 README.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/README.md b/README.md
index 58b26b7..c7c8c8a 100644
--- a/README.md
+++ b/README.md
@@ -122,3 +122,22 @@ if problems building, execute `DOCKER_BUILDKIT=0` with.
 ``` bash
  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}",
+...
+```