This tutorial is part 2 of 2 in the series.
- Part 1: How to install Docker on MacOS
Just recently I had to use Docker for my Node.js web application development. Here I want to give you a brief walkthrough on how to achieve it. First of all, we need a Node.js application. Either take your own Node.js application, or take this minimal Node.js application or this minimal Node.js with Express application. In this Docker tutorial, we will use the latter to visit our output in a browser later.
git clone email@example.com:rwieruch/node-express-server.gitcd node-express-servernpm installnpm start
After you have cloned and installed the Node.js project, visit it on
http://localhost:3000 to see the printed "Hello World". Everything should work as expected. Now, we will ship this Node application in a Docker container by using Docker image. First of all, create a so-called Dockerfile:
And enter the following content to the Dockerfile:
# Docker Image which is used as foundation to create# a custom Docker Image with this DockerfileFROM node:10# A directory within the virtualized Docker environment# Becomes more relevant when using Docker Compose laterWORKDIR /usr/src/app# Copies package.json and package-lock.json to Docker environmentCOPY package*.json ./# Installs all node packagesRUN npm install# Copies everything over to Docker environmentCOPY . .# Uses port which is used by the actual applicationEXPOSE 3000# Finally runs the applicationCMD [ "npm", "start" ]
Everything in this Dockerfile is read by the Docker interpreter line by line. In the end, it's the blueprint to create a your custom Docker Image suited for your application. The foundational image (here
FROM) we are using here makes sure that all Node/npm commands are available in the Dockerfile. Otherwise, if using a non related Node image, we would need to install Node in the Dockerfile ourselves before we could use the Node specific commands.
Optionally create a .dockerignore file to exclude folders and files from the Docker process. For example, the node_modules don't need to be included for the Docker image, because they will be installed in the process with
npm install (see Dockerfile). Therefore, the content of the .dockerignore file could be:
Next, create an account on the official Docker Hub. Afterward, you should have a Docker Hub username which can be used to build your first Docker image:
docker build -t <username>/node-express-server .
If the output after this command says "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?", you need to make sure that everything Docker related is set up and running properly. Even if it's running properly when printing all Docker engines with
docker-machine ls, you may need to set the environment variables for the Docker engine again.
If the build for the Docker image runs successfully, you should be able to list your images with the following command:
docker imagesREPOSITORY TAG IMAGE ID CREATED SIZE<username>/node-express-server latest 036d38e931e4 5 minutes ago 153MBnode alpine 532fd65ecacd 9 days ago 113MBhello-world latest fce289e99eb9 13 months ago 1.84kB
This Docker image is everything you need to run a Docker application in a Docker container. One Docker image can be used to start multiple Docker containers which helps to scale application size horizontally or to run applications with different container configuration. For now, we will only run one Docker container based on this Docker image:
docker run --name node-express-server -p 4680:3000 -d <username>/node-express-server
This command creates and runs a Docker container with a specific name, a mapping of two ports, and a Docker image. Even though the Dockerfile defines a specific port, we can redirect this to a custom port for this particular Docker container. After creating and running the Docker container based on the Docker image, we should be able to list all Docker containers:
docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESab03066fb631 <username>/node-express-server "docker-entrypoint.s…" 9 minutes ago Up 9 minutes 0.0.0.0:4680->3000/tcp/tcp node-express-server
Before we can visit our application in the browser, we need to find out the IP address of our running Docker engine:
docker-machine ip default-> 192.168.99.100
Finally you should be able to visit
http://192.168.99.100:4680. Beware that your IP address and port may vary. Congratulations, you have shipped your first Node.js web app in a Docker container.