Docker를 활용한 컨테이너화

Docker helps you package your applications and all their dependencies into standardized units called containers. Think of it as a lightweight virtual machine, but much more efficient!

For Clojure developers, Docker ensures your application runs exactly the same way on your machine, a teammate's machine, or in the cloud. No more "it works on my machine" problems!

At Docker's core are two main concepts:

• Images: These are read-only templates, like a blueprint for your application. They contain your code, libraries, and runtime.
• Containers: These are runnable instances of an image. You can start, stop, move, or delete a container without affecting the image.

A Dockerfile is a script that tells Docker how to build an image.

Every Dockerfile starts with a FROM instruction. This specifies the base image your application will build upon. For Clojure, an OpenJDK (Java Development Kit) image is a great choice.

The WORKDIR instruction sets the default directory for subsequent commands in the image.

Our Clojure web app will need a library to handle HTTP requests. We'll use Ring's Jetty adapter. This dependency is declared in your deps.edn file, which Clojure uses for dependency management.

We define a map where keys are library names and values specify their version. This tells Clojure how to find and download the necessary code.

Now, let's write a minimal Clojure web server. This file, src/server.clj, will be the entry point for our application. It starts a Jetty server that listens on port 3000 and responds with "Hello from Docker!".

Try running it locally first (after setting up deps.edn and running clojure -P):

Next, we copy our deps.edn and source code into the container. It's good practice to copy deps.edn first and run clojure -P. If deps.edn doesn't change, Docker can reuse this layer, making builds faster.

Then, we copy the rest of our project files.

For a web app, we need to tell Docker which port our application listens on. The EXPOSE instruction documents this. Then, CMD specifies the command to execute when the container starts, launching our Clojure app.

Our Clojure app runs the -main function in the server namespace.

With the Dockerfile and our Clojure project ready, we can now build the Docker image. Navigate to your project's root directory (where Dockerfile, deps.edn, and src are located) and run this command:

• -t tags your image with a name and optional version.
• . tells Docker to look for the Dockerfile in the current directory.

Once the image is built, you can run it as a container. We'll use the -p flag to map a port on your host machine (e.g., 8080) to the port inside the container (3000, as exposed by our app).

After running, open your browser to http://localhost:8080 to see your Clojure app!

Containerizing your Clojure applications offers many benefits:

• Consistency: Your app runs the same everywhere.
• Isolation: Containers isolate your app from other apps and the host system.
• Portability: Easily move your app between different environments.
• Scalability: Quickly spin up multiple instances of your app.

This makes deployment and management much simpler for Clojure services.

Which of the following Dockerfile instructions are correctly described?

You've learned how Docker helps package Clojure applications for consistent deployment. We covered:

• The core concepts of Images and Containers.
• Writing a Dockerfile with key instructions like FROM, WORKDIR, COPY, RUN, EXPOSE, and CMD.
• Building a Docker image and running it as a container.

This knowledge is crucial for deploying robust Clojure microservices!