Skip to content
Node.js sample project for trying out the VS Code Remote - Containers extension
Dockerfile JavaScript
Branch: master
Clone or download
Latest commit 6bad59b Aug 14, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.devcontainer fix typo in comment Aug 11, 2019
.vscode ts => js Apr 18, 2019
.eslintrc.json ts => js Apr 18, 2019
.gitattributes Add .gitattributes to avoid line ending issues May 3, 2019
.gitignore Initial Apr 17, 2019
LICENSE Default to a non-root user Aug 5, 2019
package.json Update package.json Apr 26, 2019
server.js ts => js Apr 18, 2019
yarn.lock ts => js Apr 18, 2019

Try Out Development Containers: Node.js

This is a sample project that lets you try out the VS Code Remote - Containers extension in a few easy steps.

Note: If you're following the quick start, you can jump to the Things to try section.

Setting up the development container

Follow these steps to open this sample in a container:

  1. If this is your first time using a development container, please follow the getting started steps.

  2. Linux users: Update USER_UID and USER_GID in .devcontainer/Dockerfile and "runArgs": [ "-u": "1000" ] in .devcontainer/devcontainer.json with your user UID/GID if not 1000 to avoid creating files as root.

  3. If you're not yet in a development container:

    • Clone this repository.
    • Press F1 and select the Remote-Containers: Open Folder in Container... command.
    • Select the cloned copy of this folder, wait for the container to start, and try things out!

Things to try

One you have this sample opened in a container, you'll be able to work with it like you would locally.

Note: This container runs as a non-root user with sudo access by default. Comment out "runArgs":["-u", "1000"] in .devcontainer/devcontainer.json if you'd prefer to run as root.

Some things to try:

  1. Edit:
    • Open server.js
    • Try adding some code and check out the language features. Notice that eslint and the vscode-eslint extension are already installed in the container.
  2. Terminal: Press Ctrl+Shift+` and type uname and other Linux commands from the terminal window.
  3. Build, Run, and Debug:
    • Open server.js
    • Add a breakpoint (e.g. on line 20).
    • Press F5 to launch the app in the container.
    • Once the breakpoint is hit, try hovering over variables, examining locals, and more.
    • Continue, then open a local browser and go to http://localhost:3000 and note you can connect to the server in the container.
  4. Forward another port:
    • Stop debugging and remove the breakpoint.
    • Open server.js
    • Change the server port to 5000. (const PORT = 5000;)
    • Press F5 to launch the app in the container.
    • Press F1 and run the Remote-Containers: Forward Port from Container... command.
    • Select port 5000.
    • Click "Open Browser" in the notification that appears to access the web app on this new port.


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.


Copyright © Microsoft Corporation All rights reserved.
Licensed under the MIT License. See LICENSE in the project root for license information.

You can’t perform that action at this time.