Skip to content

Latest commit

 

History

History
50 lines (27 loc) · 3.44 KB

vscode_docker.md

File metadata and controls

50 lines (27 loc) · 3.44 KB
Raw

Development Inside Docker Containers

This tutorial shows how you can create containers from images or restart/stop existing containers in Visual Studio Code. You can create a custom environment for your application and directly develop inside of this environment. When you are finished with your application you can upload the docker script so anybody can run and develop your code further without any dependency problems with your current setup. More advantages are:

  • You can start multiple containers.
  • Containers can be connected to eachother, so they can communicate with for example ROS communication.
  • Something broke your container? easily restart from the image.

Note: We assume that you know how to work with Docker. If this is not the case then I recommend to first go through the docker toturial located here (Still TO DO!!!)

Contents:

1) Visual Studio Code Extensions

The following extensions are used in this module:

  • Dev Containers (Open any folder or repository inside a Docker container and take advantage of Visual Studio Code's full feature set.)
  • Docker (Makes it easy to create, manage, and debug containerized applications.)

2) Docker Side Bar

The Docker side bar can be opened using the extension icon. There you will see two important sections, the containers and the images that are currently on your system. To start a new container, right-click on one of the images and then select Run or Run Interactive as visible in the figure below.

Note: Interactive creates a container where you can open terminals or work in the container. If you only run a container, it will open and run some code that you specified and close again. Like the hello-world container in the example below. Using Run will only create the container which will echo hello-world and then close again. Using Run Interactive will be identical to Run exept it doesn't close the container.

Existing containers can also be stopped and started from the side bar. Right-click on one of the containers that is not running (red square) and press Start, when the container is running a green triangle will be shown.

Alt text Alt text Alt text

3) Attach VS Code to a Running Container

Now that we have a running container, we can attach Visual Studio Code to it or, incase you only want a terminal interface, attach a Shell. Right-click on the running container and select Attach Shell or Attach Visual Studio Code. In the case of Attach Visual Studio Code, a new Visual Studio Code window will open which will be attached to the container. This will be visible in the green lower-left corner, denoting the image name and container name. You can now open folders or open terminals inside the container and start development inside of the container.

Alt text

Checkout One of the Other Modules

1. Working with Robotic Operating System
2. Remote development using SSH
3. Development inside Docker containers 4. Tips to increase development