Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

How Do I Create a Container Image?

Updated on 2022-12-30 GMT+08:00

The following two approaches are for you to consider. Approach 1 is for images that will only be updated occasionally whereas approach 2 is for images that will be frequently updated.

  • Approach 1: creating a snapshot. This approach involves three key steps: (1) Start a base container by running a base image (for example, Ubuntu image); (2) install the container engine software inside the base container; (3) create a snapshot of the container.
  • Approach 2: creating a Dockerfile to build an image. This approach involves two key steps: (1) Write software installation instructions into a Dockerfile; (2) run the docker build command to build an image from the Dockerfile.

Approach 1: Creating a Snapshot

This approach is suitable for images that will only be updated occasionally.

Figure 1 Creating a snapshot

Procedure:

  1. Install the container engine software on a host.
  2. Start an empty base container in the interactive mode.

    For example, start a CentOS container in the interactive mode.

    docker run -it centos

  3. Run the following commands to install the target software:

    yum install XXX

    git clone https://github.com/lh3/bwa.git

    cd bwa;make

    NOTE:

    Install Git in advance and check whether an SSH key is set on the local host.

  4. Run the exit command to exit the container.
  1. Create a snapshot.
    docker commit -m "xx" -a "test" container-id test/image:tag
    • -a: indicates the author of the base image.
    • container-id: indicates the ID of the container you have started in step 2. You can run the docker ps -a command to query the container ID.
    • -m: indicates the commit message.
    • test/image:tag: indicates the repository name/image name:tag name.
  1. Run the docker images command to list the built container image.

Approach 2: Creating a Dockerfile to Build an Image

This approach is suitable for images that will be frequently updated. In Approach 1, you create a snapshot of the whole container. This could be demanding if you need to frequently update your images. In this case, Approach 2 is put forward to automate the image build process.

The idea behind Approach 2 is to write the process of Approach 1 into a Dockerfile and then run the docker build -t test/image:tag. command to automatically build an image from the Dockerfile. In the preceding command, . indicates the path to the Dockerfile.

Figure 2 Creating a Dockerfile to build an image

Example Dockerfile:

NOTE:

If an external network is required, ensure that network connectivity is available.

#Version 1.0.1
FROM centos:latest

# Setting the root user as the executor of subsequent commands
USER root

# Performing operations
RUN yum update -y
RUN yum install -y java

# Using && to concatenate commands
RUN touch test.txt && echo "abc" >>abc.txt

# Setting an externally exposed port
EXPOSE 80 8080 1038

# Adding a network file
ADD https://www.baidu.com/img/bd_logo1.png /opt/

# Setting an environment variable
ENV WEBAPP_PORT=9090

# Setting a work directory
WORKDIR /opt/

# Setting a start command
ENTRYPOINT ["ls"]

# Setting start parameters
CMD ["-a", "-l"]

# Setting a volume
VOLUME ["/data", "/var/www"]

# Setting the trigger operation for a sub-image
ONBUILD ADD . /app/src
ONBUILD RUN echo "on build excuted" >> onbuild.txt

Basic Syntax of Dockerfile

  • FROM:

    It is used to specify the parent image (base image) from which you are building a new image. Except annotations, a Dockerfile must start with a FROM instruction. Subsequent instructions run in this parent image environment until the next FROM instruction appears. You can create multiple images in the same Dockerfile by adding multiple FROM instructions.

  • MAINTAINER:

    It is used to specify the information about the author who creates an image, including the username and email address. This parameter is optional.

  • RUN:

    It is used to modify an image. Generally, RUN commands are executed to install libraries, and install and configure programs. After a RUN command is executed, an image layer will be created on the current image. The next command will be executed on the new image. The RUN statement can be in one of the following formats:

    • RUN yum update: Command that is executed in the /bin/sh directory.
    • RUN ["yum", "update"]: Directly invoke exec.
    • RUN yum update && yum install nginx: Use && to connect multiple commands to a RUN statement.
  • EXPOSE:

    It is used to specify one or more network ports that will be exposed on a container. If there are multiple ports, separate them by spaces.

    When running a container, you can set -P (uppercase) to map the ports specified in EXPOSE to random ports on a host. Other containers or hosts can communicate with the container through the ports on the host.

    You can also use -p (lowercase) to expose the ports that are not listed in EXPOSE.

  • ADD:

    It is used to add a file to a new image. The file can be a host file, a network file, or a folder.

    • First parameter: source file (folder)
      • If a relative path is used, this path must correspond to the directory where the Dockerfile is located.
      • If a URL is used, the file needs to be downloaded first and then added to the image.
    • Second parameter: target path
      • If the source file is in the .zip or .tar file, the container engine decompresses the file and then adds it to the specified location of the image.
      • If the source file is a compressed network file specified by a URL, the file will not be decompressed.
  • VOLUME:

    It is used to create a mount point for a specified path (file or folder) in the image. Multiple containers can share data through the same mount point. Even if one of the containers is stopped, the mount point can still be accessed.

  • WORKDIR:

    It is used to specify a new work directory for the next command. The directory can be an absolute or a relative directory. WORKDIR can be specified multiple times as required. When a container is started, the directory specified by the last WORKDIR command is used as the current work directory of the container.

  • ENV:

    It is used to set an environment variable for running the container. When running the container, you can set -e to modify the environment variable or add other environment variables.

    Example:

    docker run -e WEBAPP_PORT=8000 -e WEBAPP_HOST=www.example.com ...

  • CMD:

    It is used to specify the default command for starting a container.

  • ENTRYPOINT:

    It is used to specify the default command for starting a container. Difference: For ENTRYPOINT, parameters added to the image during container running will be spliced. For CMD, these parameters will be overwritten.

    • If the Dockerfile specifies that the default command for starting a container is ls -l, the default command ls -l will be run accordingly. For example:
      • ENTRYPOINT [ "ls", "-l"]: The program and parameter for starting a container are set to be ls and -l respectively.
      • docker run centos: The docker run centos ls -l command is run by default for starting a CentOS container.
      • docker run centos -a: When the -a parameter is added for starting a CentOS container, the docker run centos ls -l -a command is run by default.
    • If the Dockerfile specifies that the default command for starting a container is --entrypoint but you need to replace the default command, you can add --entrypoint parameters to replace the configuration specified in Dockerfile. Example:

      docker run gutianlangyu/test --entrypoint echo "hello world"

  • USER:

    It is used to specify the user or UID for running the container, and running the RUN, CMD, or ENTRYPOINT command.

  • ONBUILD:

    Trigger command. During image build, the image builder of the container engine saves all commands specified by the ONBUILD command to the image metadata. These commands will not be executed in the process of building the current image. These commands will be executed only when a new image uses the FROM instruction to specify the parent image as the current image.

    Using the FROM instruction to build a child image based on the parent image created by the Dockerfile:

    ONBUILD ADD. /app/src: The ADD. /app/src command is automatically executed.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback