Browse Source

Add devcontainer configuration

We already have everything needed to work inside a container, with this
configuration file developing in moby is even easier: the IDE will ask
you if you want to run everything inside a container and set it up for
you. No need to know that you have to run "BIN_DIR=. make shell" any
more.

Signed-off-by: Djordje Lukic <djordje.lukic@docker.com>
Djordje Lukic 1 year ago
parent
commit
279e6658ac
2 changed files with 15 additions and 0 deletions
  1. 13 0
      .devcontainer/devcontainer.json
  2. 2 0
      docs/contributing/set-up-dev-env.md

+ 13 - 0
.devcontainer/devcontainer.json

@@ -0,0 +1,13 @@
+{
+  "name": "moby",
+  "build": {
+    "context": "..",
+    "dockerfile": "../Dockerfile",
+    "target": "dev"
+  },
+  "workspaceFolder": "/go/src/github.com/docker/docker",
+  "workspaceMount": "source=${localWorkspaceFolder},target=/go/src/github.com/docker/docker,type=bind,consistency=cached",
+
+  "remoteUser": "root",
+  "runArgs": ["--privileged"]
+}

+ 2 - 0
docs/contributing/set-up-dev-env.md

@@ -136,6 +136,8 @@ can take over 15 minutes to complete.
 
    At this point, your prompt reflects the container's BASH shell.
 
+   Alternatively you can use the provided devcontainer in an IDE that supports them (VSCode, Goland, etc.)
+
 5. List the contents of the current directory (`/go/src/github.com/docker/docker`).
 
    You should see the image's source from the  `/go/src/github.com/docker/docker`