การจัดคอนเทนเนอร์ด้วย Docker

Welcome to containerization with Docker! Docker helps package your application and its dependencies into a single unit called a container.

This ensures your app runs consistently across different environments, from your laptop to production servers.

Think of a Docker Image as a blueprint or a template. It's a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings.

A Docker Container is a running instance of an image. You can have multiple containers running from the same image, each isolated from the others.

Docker offers significant advantages for Node.js applications:

• Consistency: No more 'it works on my machine' issues.
• Isolation: Your Node.js app runs in its own environment, preventing conflicts.
• Dependencies: Easily manage and package all your npm dependencies.
• Scalability: Quickly deploy and scale identical instances of your app.

A Dockerfile is a simple text file that contains a set of instructions. These instructions tell Docker how to build your application's image.

It defines everything from the base operating system to copying files, installing dependencies, and specifying how your application should start.

Let's create a minimal Node.js application that we'll containerize. This simple server will respond with 'Hello from Node.js in Docker!' on port 3000.

You can run this code to see it working locally before Dockerizing.

Every Dockerfile starts with a FROM instruction, specifying the base image. For Node.js, we often use official Node.js images. WORKDIR sets the working directory inside the container.

Next, we copy package.json and package-lock.json (if present) to install dependencies. Then, we copy the rest of our application files. This order optimizes Docker's caching.

• COPY package*.json ./: Copies package files.
• RUN npm install: Installs dependencies.
• COPY . .: Copies all other app files.

Finally, we tell Docker which port our application listens on using EXPOSE. This is documentation, not a firewall rule. CMD defines the command to run when the container starts.

With your Dockerfile ready (and your app.js and package.json in the same directory), you can build the image. The -t flag tags your image with a name (e.g., my-node-app).

Open your terminal and run:

After building, you can run your application in a Docker container. The -p 3000:3000 flag maps port 3000 on your host machine to port 3000 inside the container.

Visit http://localhost:3000 in your browser after running:

Which of the following Dockerfile instructions are primarily used to manage dependencies and application files within the image?

You've learned the basics of Docker containerization! We covered:

• What Docker Images and Containers are.
• The benefits of Docker for Node.js apps.
• How to write a Dockerfile for a Node.js application.
• Commands to build an image and run a container.

Docker provides a powerful way to ensure your applications are consistent and easily deployable.