Fly Friday - Customizing with Dockerfiles

We deployed Docker’s official httpd image in our first Fly Friday video. That image, when run, serves up files from its /usr/local/apache2/html. By default the image contains the words “It works”. If we want it to say something else, we need to copy

Fly.io logo
Fly.io
•
Dj Walker-Morgan
•2 min read•beginner•
--
•View Original
DockerGraphQLHTML

Overview

The article discusses how to customize a Docker image deployed to Fly using a simple Dockerfile. It provides a step-by-step guide on modifying the default content served by the Docker httpd image by copying local files into the image's directory.

What You'll Learn

1

How to customize a Docker image using a Dockerfile

2

Why using the COPY command in Dockerfiles is essential for modifying content

3

When to create a public_html directory for serving custom content

Key Questions Answered

How can I customize the content served by a Docker httpd image?
You can customize the content served by a Docker httpd image by creating a Dockerfile that uses the COPY command to transfer your local HTML files into the image's /usr/local/apache2/htdocs/ directory. This allows you to replace the default content with your own.
What is the purpose of the FROM command in a Dockerfile?
The FROM command in a Dockerfile specifies the base image to use for building a new image. In this case, it indicates that the Docker httpd image will be the foundation for the customized image.
What should I do to serve custom HTML content using Docker?
To serve custom HTML content using Docker, create a public_html directory with your HTML files and write a Dockerfile that copies this directory into the appropriate location in the Docker httpd image. This will ensure your content is served when the image is deployed.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Containerization
Docker
Used to create and manage the customized Docker image.
Web Server
Httpd
The base image used to serve web content.

Key Actionable Insights

1
Create a Dockerfile with minimal lines to customize your Docker image effectively.
Using a concise Dockerfile allows for quick modifications and deployment, making it easier to manage changes in your web content.
2
Utilize the COPY command to transfer local files into your Docker image.
This command is crucial for ensuring that your specific content is served instead of the default, enhancing the user experience.
3
Set up a public_html directory to organize your HTML files.
Having a dedicated directory for your content keeps your project organized and simplifies the process of updating or replacing files.

Common Pitfalls

1
Failing to create the public_html directory before building the Docker image.
If the directory is not created, the COPY command will not find the files to transfer, resulting in an incomplete image that cannot serve your custom content.