Official Repository

Last pushed: a month ago
Short Description
The official build of CentOS.
Full Description

Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/centos). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/centos/tag-details.md file in the docker-library/repo-info GitHub repo.

CentOS

CentOS Linux is a community-supported distribution derived from sources freely provided to the public by Red Hat for Red Hat Enterprise Linux (RHEL). As such, CentOS Linux aims to be functionally compatible with RHEL. The CentOS Project mainly changes packages to remove upstream vendor branding and artwork. CentOS Linux is no-cost and free to redistribute. Each CentOS Linux version is maintained for up to 10 years (by means of security updates -- the duration of the support interval by Red Hat has varied over time with respect to Sources released). A new CentOS Linux version is released approximately every 2 years and each CentOS Linux version is periodically updated (roughly every 6 months) to support newer hardware. This results in a secure, low-maintenance, reliable, predictable, and reproducible Linux environment.

wiki.centos.org

CentOS image documentation

The centos:latest tag is always the most recent version currently available.

Rolling builds

The CentOS Project offers regularly updated images for all active releases. These images will be updated monthly or as needed for emergency fixes. These rolling updates are tagged with the major version number only. For example: docker pull centos:6 or docker pull centos:7

Minor tags

Additionally, images with minor version tags that correspond to install media are also offered. These images DO NOT recieve updates as they are intended to match installation iso contents. If you choose to use these images it is highly recommended that you include RUN yum -y update && yum clean all in your Dockerfile, or otherwise address any potential security concerns. To use these images, please specify the minor version tag:

For example: docker pull centos:5.11 or docker pull centos:6.6

Overlayfs and yum

Recent Docker versions support the overlayfs backend, which is enabled by default on most distros supporting it from Docker 1.13 onwards. On Centos 6 and 7, that backend requires yum-plugin-ovl to be installed and enabled; while it is installed by default in recent centos images, make it sure you retain the plugins=1 option in /etc/yum.conf if you update that file; otherwise, you may encounter errors related to rpmdb checksum failure - see Docker ticket 10180 for more details.

Package documentation

By default, the CentOS containers are built using yum's nodocs option, which helps reduce the size of the image. If you install a package and discover files missing, please comment out the line tsflags=nodocs in /etc/yum.conf and reinstall your package.

Systemd integration

Systemd is now included in both the centos:7 and centos:latest base containers, but it is not active by default. In order to use systemd, you will need to include text similar to the example Dockerfile below:

Dockerfile for systemd base image

FROM centos:7
MAINTAINER "you" <your@email.here>
ENV container docker
RUN (cd /lib/systemd/system/sysinit.target.wants/; for i in *; do [ $i == \
systemd-tmpfiles-setup.service ] || rm -f $i; done); \
rm -f /lib/systemd/system/multi-user.target.wants/*;\
rm -f /etc/systemd/system/*.wants/*;\
rm -f /lib/systemd/system/local-fs.target.wants/*; \
rm -f /lib/systemd/system/sockets.target.wants/*udev*; \
rm -f /lib/systemd/system/sockets.target.wants/*initctl*; \
rm -f /lib/systemd/system/basic.target.wants/*;\
rm -f /lib/systemd/system/anaconda.target.wants/*;
VOLUME [ "/sys/fs/cgroup" ]
CMD ["/usr/sbin/init"]

This Dockerfile deletes a number of unit files which might cause issues. From here, you are ready to build your base image.

$ docker build --rm -t local/c7-systemd .

Example systemd enabled app container

In order to use the systemd enabled base container created above, you will need to create your Dockerfile similar to the one below.

FROM local/c7-systemd
RUN yum -y install httpd; yum clean all; systemctl enable httpd.service
EXPOSE 80
CMD ["/usr/sbin/init"]

Build this image:

$ docker build --rm -t local/c7-systemd-httpd

Running a systemd enabled app container

In order to run a container with systemd, you will need to mount the cgroups volumes from the host. Below is an example command that will run the systemd enabled httpd container created earlier.

$ docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 local/c7-systemd-httpd

This container is running with systemd in a limited context, with the cgroups filesystem mounted. There have been reports that if you're using an Ubuntu host, you will need to add -v /tmp/$(mktemp -d):/run in addition to the cgroups mount.

Supported Docker versions

This image is officially supported on Docker version 1.13.0.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us by submitting a ticket at https://bugs.centos.org or through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans by submitting a ticket at https://bugs.centos.org or through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Documentation

Documentation for this image is stored in the centos/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

Docker Pull Command

Comments (146)
herobigdata
20 days ago

Hello, how to solve : Failed to get D-Bus connection: Operation not permitted ? thanks !

jamshid
a month ago

If you're having problems with yum / checksum errors, make sure your docker server is using overlay2 and you install yum-plugin-ovl (https://github.com/CentOS/sig-cloud-instance-images/issues/74).

If you are having problems running systemd, see:
https://github.com/docker/docker/issues/28614#issuecomment-261724902

docmiller
a month ago

For those experiencing issues with systemctl I recommend running "yum reinstall systemd" or dnf if you are using that.

canit0
2 months ago

@jnmik like what does that even mean? If you download an install DVD, are you going to ask that they provide a vulnerability free image, or simply patch it yourself once you install the OS?

jnmik
2 months ago

Any plans to make the latest image vulnerability free ?

ghadsfjkghf
3 months ago

aa

cristo
5 months ago

I have a problem with centos:7.2.1511

Rpmdb checksum is invalid: dCDPT(pkg checksums): perl-HTTP-Tiny.noarch 0:0.033-3.el7 - u

Removing intermediate container f0a55f9f7775
The command '/bin/sh -c yum install -y git' returned a non-zero code: 1

jperrin
5 months ago

As a reminder, if you're having issues with the CentOS base container, please submit them via https://github.com/CentOS/sig-cloud-instance-images/issues

This page on hub.docker doesn't support issue tracking, notifications, etc. and so issues may be missed. If they're posted on github we can better track and resolve them.

mpender
6 months ago

Using OSX (Yosemite) and docker toolbox for this, getting :
/bin/sh: line 0: [: cryptsetup.target: unary operator expected
/bin/sh: line 0: [: dev-hugepages.mount: unary operator expected
/bin/sh: line 0: [: dev-mqueue.mount: unary operator expected
/bin/sh: line 0: [: kmod-static-nodes.service: unary operator expected
/bin/sh: line 0: [: proc-sys-fs-binfmt_misc.automount: unary operator expected
/bin/sh: line 0: [: sys-fs-fuse-connections.mount: unary operator expected
/bin/sh: line 0: [: sys-kernel-config.mount: unary operator expected

When building the image which is odd

Have not seen an implementation (Debian or CentOS) that works. anyone with similar issues?
Docker version 1.11.2, build b9f10c9

clementfarnier
6 months ago

Hello,

Use systemd in container based on centos7 image works well.
But impossible to use systemd in Dockerfiles based on centos7 image (with the "FROM c7-systemd" on top of the Dockerfile), which is a problem if we have an application to install in a Dockerfile which needs to start and stop services.

Thanks.