Chapter 13. Creating a Container with an Application
This section describes how to create a docker-formatted container image from a locally built application. Making your application available as a container is advantageous when you wish to use orchestration for deployment. Alternatively, containerizing effectively solves conflicts of dependencies.
- Understanding of containers
- An application built locally from source
Decide which base image to use.Note
Red Hat recommends starting with a base image that uses Red Hat Enterprise Linux as its foundation. Refer to the Base Image in the Red Hat Container Catalog for further information.
- Create a workspace directory.
- Prepare your application as a directory containing all of the application’s required files. Place this directory inside the workspace directory.
Write a Dockerfile that describes the steps required to create the container.
Refer to the Dockerfile Reference for information about how to create a Dockerfile that includes your content, sets default commands to run, and opens necessary ports and other features.
This example shows a minimal Dockerfile that contains the
FROM registry.access.redhat.com/rhel7 USER root ADD my-program/ .
Place this Dockerfile into the workspace directory.
Build a container image from the Dockerfile:
# docker build . (...) Successfully built container-id
During this step, note the container-id of the newly created container image.
Add a tag to the image to identify the registry where you want the container image to be stored. See Getting Started with Containers — Tagging Images.
# docker tag container-id registry:port/name
Replace container-id with the value shown in the output of the previous step.
Replace registry with the address of the registry you want to push the image to, port with the port of the registry (omit if not needed), and name with the name of the image.
For example, if you are running a registry using the
docker-distributionservice on your local system with an image named myimage, the tag localhost:5000/myimage would enable that image to be pushed to the registry.
Push the image to the registry so it can be pulled from that registry later.
# docker push registry:port/name
Replace the tag parts with the same values as the ones used in the previous step.
To run your own Docker registry, see Getting Started with Containers — Working with Docker registries.
- OpenShift Container Platform — Develop: Images
- Red Hat Enterprise Linux Atomic Host — Recommended Practices for Container Development
- Dockerfile Reference
- Docker Documentation — Get Started, Part 2: Containers
- Red Hat Enterprise Linux Atomic Host — Getting Started with Containers
- Red Hat Container Catalog listing — Base Images