From 4982d2ecd8c6d7b50b3f3048df441e7c4135bc98 Mon Sep 17 00:00:00 2001 From: Nicolas Munnich <98408764+Nick-Munnich@users.noreply.github.com> Date: Tue, 21 May 2024 18:03:33 +0200 Subject: [PATCH] Moved info Co-authored-by: Cem Aksoylar --- docs/docs/development/setup/docker.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/docs/development/setup/docker.md b/docs/docs/development/setup/docker.md index 1b1f26b3..61077091 100644 --- a/docs/docs/development/setup/docker.md +++ b/docs/docs/development/setup/docker.md @@ -33,14 +33,10 @@ Open the `zmk` checkout folder in VS Code. The repository includes a configurati ![VS Code Dev Container Configuration Alert](../../assets/dev-setup/vscode_devcontainer.png) -Click `Reopen in Container` in order to reopen the VS Code with the running container. +Click `Reopen in Container` in order to reopen the VS Code with the running container. If the alert fails to pop up or you accidentally close it, you can perform the same action by pressing `ctrl+shift+p` and selecting `Remote: Show Remote Menu`. The first time you do this on your machine, it will pull the docker image down from the registry and build the container. Subsequent launches are much faster! -:::note -If the alert fails to pop up or you accidentally close it, you can perform the same action from the remote menu: `ctrl+shift+p` and invoke `Remote: Show Remote Menu`. -::: - :::caution All subsequent steps must be performed from the VS Code terminal _inside_ the container. :::