Debug a Node.js Application Running in a Docker Container
This article shows how you can debug a simple Node.js application running in a Docker container. Use this tutorial as a reference while building your own!
Join the DZone community and get the full member experience.
Join For FreeThis blog post shows how you can debug a simple Node.js application running in a Docker container. The tutorial is laid out in a fashion that allows you to use it as a reference while you’re building your own Node.js application and is intended for readers who have prior exposure to JavaScript programming and Docker.
Prerequisites
- Docker. For details about installing Docker, refer to the Install Docker page.
- Node.js 10 or higher. To check out if Node.js is installed on your computer, fire up a terminal window and type the following command:
node -v
If Node.js is already installed, you'll see something like the following:
xxxxxxxxxx
v10.15.3
If Node.js is not installed, you can download the installer from the Download page.
- Microsoft Visual Studio. For details on how to install Visual Studio, refer to the Install Visual Studio page.
Initializing Your Todo Application
For the scope of this tutorial, we’ll create a bare-bones todo list that allows users to add and delete tasks. There will be a small bug in the application and we’ll use Visual Studio Code to debug the code and fix the issue. The knowledge you’ll acquire in this tutorial will help you debug your own applications. Let’s get started.
- Fire up a new terminal window, move into your projects directory, and then execute the following command:
xxxxxxxxxx
mkdir MyTodoApp && cd MyTodoApp
2. Initialize the project with:
xxxxxxxxxx
npm init -y
This will output something like the following:
xxxxxxxxxx
Wrote to /Users/ProspectOne/Documents/MyTodoApp/package.json:
{
"name": "MyTodoApp",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC"
}
Creating a Bare-bones Todo Application
We’ll build our todo application using Express, a fast, unopinionated, minimalist web framework for Node.js. Express was designed to make developing websites much easier and it’s one of the most popular Node.js web frameworks.
- Install
expressand a few other prerequisites by entering the following command:
xxxxxxxxxx
npm install express body-parser cookie-session ejs --save
xxxxxxxxxx
> ejs@3.0.1 postinstall /Users/ProspectOne/Documents/test/MyTodoApp/node_modules/ejs
> node ./postinstall.js
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN MyTodoApp@1.0.0 No description
npm WARN MyTodoApp@1.0.0 No repository field.
+ ejs@3.0.1
+ body-parser@1.19.0
+ express@4.17.1
+ cookie-session@1.3.3
added 55 packages from 39 contributors and audited 166 packages in 6.533s
found 0 vulnerabilities
2. Create a file called app.js with the following content:
xxxxxxxxxx
const express = require('express')
const app = express()
const bodyParser = require('body-parser')
const session = require('cookie-session')
const urlencodedParser = bodyParser.urlencoded({ extended: false })
const port = 3000
app.use(session({ secret: process.env.SECRET }))
.use(function (req, res, next) {
next()
})
.get ('/todo', function (req, res) {
res.render('todo.ejs', { todolist: req.session.todolist })
})
.post ('/todo/add/', urlencodedParser, function (req, res) {
if (req.body.newtodo != '') {
req.session.todolist.push(req.body.newtodo)
}
res.redirect('/todo')
})
.get ('/todo/delete/:id', function (req, res) {
if (req.params.id != '') {
req.session.todolist.splice(req.params.id, 1)
}
res.redirect('/todo')
})
.use (function (req, res, next) {
res.redirect('/todo')
})
.listen(port, () => console.log(`MyTodo app is listening on port ${port}!`))
Note that the above snippet is a derivative work of the code from the openclassroom.com website and explaining how this code works is beyond the scope of this tutorial. If the details are fuzzy, we recommend you check out their site to further your learning after you finish this tutorial.
- Create a file called
./views/todo.ejsand paste into it the following content:
xxxxxxxxxx
<!DOCTYPE html>
<html>
<head>
<title>My todolist</title>
<style>
a {text-decoration: none; color: black;}
</style>
</head>
<body>
<h1>My todolist</h1>
<ul>
<% todolist.forEach(function(todo, index) { %>
<li><a href="/todo/delete/<%= index %>">✘</a> <%= todo %></li>
<% }); %>
</ul>
<form action="/todo/add/" method="post">
<p>
<label for="newtodo">What should I do?</label>
<input type="text" name="newtodo" id="newtodo" autofocus />
<input type="submit" />
</p>
</form>
</body>
</html>
4. At this point, your directory structure should look something like the following:
xxxxxxxxxx
tree -L 2 -I node_modules
xxxxxxxxxx
.
├── app.js
├── package-lock.json
├── package.json
└── views
└── todo.ejs
1 directory, 4 files
5. Now you are ready to start your web server by entering:
xxxxxxxxxx
SECRET=bestkeptsecret; node app.js
This will print out the following message to the console:
xxxxxxxxxx
MyTodo app is listening on port 3000!
Create a Docker Image
Now that you’ve written the Todo application, it's time to add create a Docker image for it. Each Docker container is based on a Docker image that contains all the information needed to deploy and run your app with Docker. To run a Docker container you can:
- Download an existing Docker image
- Create your own image
In this tutorial, you'll create your own image. Note that a Docker image is usually comprised of multiple layers and each layer is basically a read-only filesystem. The way this works is that Docker creates a layer for each instruction found in the Dockerfile and places it atop of the previous layers. It is considered good practice to place the application’s code, that changes often, closer to the bottom of the file.
- Create a file called
Dockerfileand paste the following snippet into it:
xxxxxxxxxx
FROM node:10
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000
CMD [ "node", "app.js" ]
Let’s take a closer look at this file:
- FROM: sets the base image. Everything you’ll add later on it’ll be based on this image. In this example, we’re using Node.js version 10.
- WORKDIR: this command sets the working directory that’ll be used for the COPY, RUN, and CMD commands.
- RUN: this line of code runs the
npm installcommand inside your Docker container. - COPY: copies files from the build context into the Docker image
- EXPOSE: specifies that a process running inside the container is listening to the 3000 port. This will be useful later in this tutorial when you’ll forward ports from the host to the container.
- CMD: this line runs the
node app.jsinside your Docker container only after the container has been started.
- To avoid sending large files to the build context and speed up the process, you can use a
.dockerignorefile. This is nothing more than a plain text file that contains the name of the files and directories that should be excluded from the build. You can think of it as something similar to a.gitignorefile. Create a file called.dockerignorewith the following content:
xxxxxxxxxx
node_modules
npm-debug.log
- Now you can go ahead and build your Docker image by entering the
docker buildcommand followed by:
- The
-tparameter which specifies the name of the image - The path to the context which should point to the set of files you want to reference from your Dockerfile
xxxxxxxxxx
docker build -t prospectone/my-todo-list .
xxxxxxxxxx
Sending build context to Docker daemon 24.58kB
Step 1/7 : FROM node:10
---> c5d0d6dc0b5b
Step 2/7 : WORKDIR /usr/src/app
---> Using cache
---> 508b797a892e
Step 3/7 : COPY package*.json ./
---> 0b821f725c19
Step 4/7 : RUN npm install
---> Running in d692a6278d2b
> ejs@3.0.1 postinstall /usr/src/app/node_modules/ejs
> node ./postinstall.js
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
npm WARN MyTodoApp@1.0.0 No description
npm WARN MyTodoApp@1.0.0 No repository field.
added 55 packages from 39 contributors and audited 166 packages in 2.564s
found 0 vulnerabilities
Removing intermediate container d692a6278d2b
---> 067de030e269
Step 5/7 : COPY . .
---> 3141ccb6e094
Step 6/7 : EXPOSE 3000
---> Running in eb824e38d8c6
Removing intermediate container eb824e38d8c6
---> b09d55adc1c4
Step 7/7 : CMD [ "node", "app.js" ]
---> Running in 7e77e0cbfa75
Removing intermediate container 7e77e0cbfa75
---> c0a2db4c7a65
Successfully built c0a2db4c7a65
Successfully tagged prospectone/my-todo-list:latest
As mentioned above, the way the docker build command works is that it adds a new layer for each command in your Dockerfile. Then, once a command is successfully executed, Docker deletes the intermediate container.
- Now that you’ve built your image, let’s run it by entering the
docker runcommand and passing it the following arguments:
-pwith the port on the host (3001) that’ll be forwarded to the container (3000), separated by:-eto create an environment variable calledSECRETand set its value tobestkeptsecret-dto specify that the container should be run in the background- The name of the image (
prospectone/my-awesome-app)
xxxxxxxxxx
docker run -p 3001:3000 -e SECRET=bestkeptsecret -d prospectone/my-todo-list
xxxxxxxxxx
db16ed662e8a3e0a93f226ab873199713936bd687a4546d2fce93e678d131243
5. You can verify that your Docker container is running with:
xxxxxxxxxx
docker ps
The output should be similar to:
xxxxxxxxxx
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a6eb166191c7 prospectone/my-todo-list "docker-entrypoint.s…" 4 seconds ago Up 3 seconds 0.0.0.0:3001->3000/tcp happy_hawking
6. To inspect the logs, enter the docker logs command followed by the id of your container:
xxxxxxxxxx
docker logs a6eb166191c7
xxxxxxxxxx
MyTodo app is listening on port 3000!
7. Now that your application is up and running, point your browser to http://localhost:3001 and let us add a new todo. As you can see below, the application errors out on line 15 of the todo.ejs file:
In the next sections, you’ll learn how to debug this using Visual Studio Code.
- But first, stop the container with:
xxxxxxxxxx
docker kill a6eb166191c7
xxxxxxxxxx
a6eb166191c7
Enable Debugging in Microsoft Visual Studio Code
Visual Studio Code provides debugging support for the Node.js applications running inside a Docker container. Follow the next steps to enable this feature:
- Edit your Dockerfile by replacing the following line:
xxxxxxxxxx
CMD [ "node", "app.js" ]
with:
xxxxxxxxxx
CMD [ "npm", "run", "start-debug" ]
Your Dockerfile should look something like the following:
xxxxxxxxxx
FROM node:10
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000
CMD [ "npm", "run", "start-debug" ]
2. Open the package.json file and add the following line to the scripts object:
xxxxxxxxxx
"start-debug": "node --inspect=0.0.0.0 app.js"
This line of code starts the Node.js process and listens for a debugging client on port 9229.
Here’s how your package.json file should look like:
xxxxxxxxxx
{
"name": "MyTodoApp",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start-debug": "node --inspect=0.0.0.0 app.js"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"body-parser": "^1.19.0",
"cookie-session": "^1.3.3",
"ejs": "^3.0.1",
"express": "^4.17.1"
}
}
3. Every time the Dockerfile gets updated, you must build again your Docker image:
xxxxxxxxxx
docker build -t prospectone/my-todo-list .
xxxxxxxxxx
Sending build context to Docker daemon 19.97kB
Step 1/7 : FROM node:10
---> c5d0d6dc0b5b
Step 2/7 : WORKDIR /usr/src/app
---> Using cache
---> 508b797a892e
Step 3/7 : COPY package*.json ./
---> c0eec534b176
Step 4/7 : RUN npm install
---> Running in a155901cb957
npm WARN MyAwesomeApp@1.0.0 No description
npm WARN MyAwesomeApp@1.0.0 No repository field.
added 50 packages from 37 contributors and audited 126 packages in 11.504s
found 0 vulnerabilities
Removing intermediate container a155901cb957
---> 010473a35e41
Step 5/7 : COPY . .
---> 76dfa12d4db4
Step 6/7 : EXPOSE 3000
---> Running in b5a334c9a2ea
Removing intermediate container b5a334c9a2ea
---> b5a869ab5441
Step 7/7 : CMD [ "npm", "run", "start-debug" ]
---> Running in 1beb2ca9a391
Removing intermediate container 1beb2ca9a391
---> 157b7d4cb77b
Successfully built 157b7d4cb77b
Successfully tagged prospectone/my-todo-list:latest
Note that Step 7 has been updated, meaning that Docker will now execute the npm run start-debug command.
- To enable debugging with Visual Studio Code, you must also forward port
9229. Start your Docker container by entering:
xxxxxxxxxx
docker run -p 3001:3000 -p 9229:9229 -e SECRET=bestkeptsecret22222 -d perfops/my-todo-list
xxxxxxxxxx
0f5860bebdb5c70538bcdd10ddc901411b37ea0c7d92283310700085b1b8ddc5
5. You can inspect the logs by entering the docker logs command followed the id of your container:
xxxxxxxxxx
docker logs 0f5860bebdb5c70538bcdd10ddc901411b37ea0c7d92283310700085b1b8ddc5
xxxxxxxxxx
> My@1.0.0 start-debug /usr/src/app
> node --inspect=0.0.0.0 app.js
Debugger listening on ws://0.0.0.0:9229/59d4550c-fc0e-412e-870a-c02b4a6dcd0f
For help, see: https://nodejs.org/en/docs/inspector
Note that the debugger is now listening to port 9229. Next, you’ll configure Visual Studio code to debug your application.
Debug Your Application with Visual Studio Code
- In Visual Studio Code, open the
MyTodoAppdirectory.
- The configuration for debugging is stored in a file called
launch.json. To open it, pressCommand+Shift+Pand then chooseDebug: Open launch.json.
- Replace the content of the
launch.jsonfile with the following snippet:
xxxxxxxxxx
{
"version": "0.2.0",
"configurations": [
{
"name": "Docker: Attach to Node",
"type": "node",
"request": "attach",
"port": 9229,
"address": "localhost",
"localRoot": "${workspaceFolder}",
"remoteRoot": "/usr/src/app",
"protocol": "inspector",
"skipFiles": [
"${workspaceFolder}/node_modules/**/*.js",
"<node_internals>/**/*.js"
]
}
]
}
Note that we’re using the skipFiles attribute to avoid stepping through the code in the node_modules directory and the built-in core modules of Node.js.
- Now everything is set up and you can start debugging your application. Remember that there was an error at line 15 in the
views.jsfile, which basically iterates over thetodolistarray:todolist.forEach(function(todo, index). Looking at theapp.jsfile you’ll see that todo.ejs gets rendered at line 14. Let’s add a breakpoint so we can inspect the value of thetodolistvariable:
- Enter
Shift+Command+Dto switch to theDebugview. Then, click theDebug and Runbutton:
- To inspect the value of the
req.session.todolistvariable, you must add a new expression to watch by selecting the+sign and then typing the name of the variable (req.session.todolist):
- Switch to the browser window and reload the http://localhost:3001 page.
Note the Waiting for localhost message at the bottom. This means that our breakpoint has paused execution and we can inspect the value of the req.session.todolist variable. Move back to Visual Studio to get details:
So the req.session.todolist variable is undefined. Can you think of how you could fix this bug? The answer is below, but don’t continue until you’ve given it some thought.
- The
ejbtemplate iterates over thetodolistarray which should be stored in the current session. But we forgot to initialize this array so it’sundefined. Let’s fix that by adding the following lines of code to the.usefunction :
xxxxxxxxxx
if (typeof (req.session.todolist) == 'undefined') {
req.session.todolist = []
}
Make sure you paste this snippet just above the line of code that calls the next function. Your .use function should look like below:
xxxxxxxxxx
app.use(session({ secret: process.env.SECRET }))
.use(function (req, res, next) {
if (typeof (req.session.todolist) == 'undefined') {
req.session.todolist = []
}
next()
})
9. Retrieve the id of your running container :
xxxxxxxxxx
docker ps
xxxxxxxxxx
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cb9f175f7af3 prospectone/my-todo-list "docker-entrypoint.s…" 15 minutes ago Up 15 minutes 0.0.0.0:9229->9229/tcp, 0.0.0.0:3001->3000/tcp nervous_hopper
10. Stop the container by entering the docker kill command followed by its id:
xxxxxxxxxx
docker kill cb9f175f7af3
xxxxxxxxxx
cb9f175f7af3
11. To apply the changes you must run the docker build command again:
xxxxxxxxxx
docker build -t prospectone/my-todo-list .
xxxxxxxxxx
Sending build context to Docker daemon 26.11kB
Step 1/7 : FROM node:10
---> c5d0d6dc0b5b
Step 2/7 : WORKDIR /usr/src/app
---> Using cache
---> 508b797a892e
Step 3/7 : COPY package*.json ./
---> Using cache
---> c5ac875da76b
Step 4/7 : RUN npm install
---> Using cache
---> 29e7b3bac403
Step 5/7 : COPY . .
---> b92f577afd57
Step 6/7 : EXPOSE 3000
---> Running in 78606a3c2e03
Removing intermediate container 78606a3c2e03
---> 59c2ed552549
Step 7/7 : CMD [ "npm", "run", "start-debug" ]
---> Running in e0313973bb5a
Removing intermediate container e0313973bb5a
---> 70a675646c0d
Successfully built 70a675646c0d
Successfully tagged prospectone/my-todo-list:latest
12. Now you can run the container with:
xxxxxxxxxx
docker run -p 3001:3000 -p 9229:9229 -e SECRET=bestkeptsecret222212 -d prospectone/my-todo-list
xxxxxxxxxx
f75d4ef8b702df13749b10615f3945ea61b36571b0dc42b76f50b3c99e14f4c6
13. Inspect the logs by running the following command:
xxxxxxxxxx
docker logs 10f467dbb476
xxxxxxxxxx
f75d4ef8b702df13749b10615f3945ea61b36571b0dc42b76f50b3c99e14f4c6
14. Reload the page and add a new task:
Congratulations, you’ve successfully written a bare-bones todo app, ran it inside a Docker container, and used Visual Studio Code to debug it and fix a bug. In the next article, we’ll walk you through the process of dockerizing an existing application.
Published at DZone with permission of Sudip Sengupta. See the original article here.
Opinions expressed by DZone contributors are their own.
Trending
-
A Complete Guide to AWS File Handling and How It Is Revolutionizing Cloud Storage
-
Five Java Books Beginners and Professionals Should Read
-
How To Use Geo-Partitioning to Comply With Data Regulations and Deliver Low Latency Globally
-
A React Frontend With Go/Gin/Gorm Backend in One Project
Comments