Images之base image
Create a base image
Most Dockerfiles start from a parent image.
If you need to completely control the contents of your image, you might need to create a base image instead.
Here’s the difference:
-
A parent image is the image that your image is based on. It refers to the contents of the
FROM
directive in the Dockerfile. Each subsequent declaration in the Dockerfile modifies this parent image. Most Dockerfiles start from a parent image, rather than a base image. However, the terms are sometimes used interchangeably. -
A base image either has no
FROM
line in its Dockerfile, or hasFROM scratch
.
This topic shows you several ways to create a base image. The specific process will depend heavily on the Linux distribution you want to package.
We have some examples below, and you are encouraged to submit pull requests to contribute new ones.
Create a full image using tar
In general, start with a working machine that is running the distribution you’d like to package as a parent image, though that is not required for some tools like Debian’s Debootstrap, which you can also use to build Ubuntu images.
It can be as simple as this to create an Ubuntu parent image:
$ sudo debootstrap xenial xenial > /dev/null $ sudo tar -C xenial -c . | docker import - xenial a29c15f1bf7a $ docker run xenial cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
Linux sudo命令以系统管理者的身份执行指令,也就是说,经由 sudo 所执行的指令就好像是 root 亲自执行。
使用权限:在 /etc/sudoers 中有出现的使用者。
debootstrap是debian/ubuntu下的一个工具,用来构建一套基本的系统(根文件系统)。生成的目录符合Linux文件系统标准(FHS),即包含了/boot、/etc、/bin、/usr等等目录,但它比发行版本的Linux体积小很多,当然功能也没那么强大,因此,只能说是“基本的系统”。
ubuntu默认没有安装debootstrap,安装十分简单,执行下列命令即可:
# sudo apt-get install debootstrap
使用也十分简单,命令格式为:
sudo debootstrap –arch [平台] [发行版本代号] [目录]
比如下面的命令
sudo debootstrap –arch i386 trusty /mnt
即是构建x86(32位)平台ubuntu最新发行版14.04(代号为trusty)的基本系统,存放到/mnt目录下。
There are more example scripts for creating parent images in the Docker GitHub Repo:
- BusyBox
- CentOS / Scientific Linux CERN (SLC) on Debian/Ubuntu or on CentOS/RHEL/SLC/etc.
- Debian / Ubuntu
Create a simple parent image using scratch
You can use Docker’s reserved, minimal image, scratch
, as a starting point for building containers.
Using the scratch
“image” signals to the build process that you want the next command in the Dockerfile
to be the first filesystem layer in your image.
While scratch
appears in Docker’s repository on the hub, you can’t pull it, run it, or tag any image with the name scratch
.
Instead, you can refer to it in your Dockerfile
.
For example, to create a minimal container using scratch
:
FROM scratch ADD hello / CMD ["/hello"]
Assuming you built the “hello” executable example by following the instructions at https://github.com/docker-library/hello-world/, and you compiled it with the -static
flag, you can build this Docker image using this docker build
command:
docker build --tag hello .
Don’t forget the .
character at the end, which sets the build context to the current directory.
Note: Because Docker for Mac and Docker for Windows use a Linux VM, you need a Linux binary, rather than a Mac or Windows binary. You can use a Docker container to build it:
$ docker run --rm -it -v $PWD:/build ubuntu:16.04 container# apt-get update && apt-get install build-essential container# cd /build container# gcc -o hello -static -nostartfiles hello.c
To run your new image, use the docker run
command:
docker run --rm hello
This example creates the hello-world image used in the tutorials. If you want to test it out, you can clone the image repo.
More resources
There are lots more resources available to help you write your Dockerfile
.
- There’s a complete guide to all the instructions available for use in a
Dockerfile
in the reference section. - To help you write a clear, readable, maintainable
Dockerfile
, we’ve also written aDockerfile
best practices guide. - If your goal is to create a new Official Repository, be sure to read up on Docker’s Official Repositories.