Sharing a Go application with someone who lacks Go installed—or whose environment differs from yours—often leads to the dreaded "it works on my machine" syndrome. Docker solves this by packaging your code and all its dependencies into a standardized container. This guide walks you through containerizing a Go app step by step, covering everything from Docker basics to multi-container orchestration with Docker Compose.
What You’ll Learn
- Prerequisites
- What Is Docker?
- Installing Docker
- Understanding the Dockerfile
- What Is Docker Compose?
- The Application Container
- The Database Container
- The phpMyAdmin Container
- Running Everything Together
Prerequisites
No previous Docker experience is required—this guide is written with beginners in mind. However, a basic understanding of Go programming will help you follow along with the code samples. If you need a refresher, check out a Go getting-started tutorial.
What Is Docker?
Imagine a box that contains your application plus everything it needs to run: the programming language runtime, libraries, environment variables, and configuration files. You can give this box to anyone, and they can run your app without installing anything extra. That box is called a Docker image. When you execute that image, you get a running instance called a container. Containers ensure that your application behaves identically regardless of the underlying host system.
Installing Docker
Docker is available for Windows, macOS, and Linux. Download the appropriate version from the Docker Desktop site for your OS. After installation, verify it by running docker --version in your terminal.
Understanding the Dockerfile
A Dockerfile is a text file containing instructions to build a Docker image. For a Go application, a typical Dockerfile might start from a Go base image, copy your source code, compile it, and then run the binary. Multi-stage builds are common to keep the final image small.
What Is Docker Compose?
Docker Compose allows you to define and run multi-container applications. Instead of manually starting each container, you write a docker-compose.yml file that describes the services (containers), networks, and volumes. With a single command, all containers spin up together.
The Application Container
Your Go app container will serve the main logic. You’ll create a Dockerfile for it, expose the port your app listens on, and optionally connect it to a database. For a REST API, you might use port 8080.
The Database Container
For a database, you can use the official MySQL or PostgreSQL image. In the Compose file, define a service with the image name, set environment variables for credentials, and mount a volume for persistent storage. The app container will connect to it via the service name.
The phpMyAdmin Container
If you need a web-based database management tool, add a phpMyAdmin container. It simply needs the MySQL service name and credentials. This container is optional but handy for development.
Running Everything Together
With all services defined in docker-compose.yml, run docker-compose up to build and start everything. Your Go app will be accessible on the configured port, and phpMyAdmin on another port. Stopping the environment is as easy as docker-compose down.
Wrapping Up
You now understand how to containerize a Go application, from crafting a Dockerfile to orchestrating multiple containers with Docker Compose. The same principles apply to any language or stack. Docker removes environment inconsistencies and streamlines sharing and deployment.