# Support official Docker packages on Red Hat/CentOS

**URL:** <https://meta.discourse.org/t/support-official-docker-packages-on-red-hat-centos/73476>\
**Category:** Feature\
**Created:** [05.Ноябрь.2017 20:05:39 UTC](https://meta.discourse.org/t/support-official-docker-packages-on-red-hat-centos/73476 "2017-11-05T20:05:39Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![leoluk](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leoluk/32/81742_2.png) [@leoluk](https://meta.discourse.org/u/leoluk)\
**Post date:** [05.Ноябрь.2017 20:05:39 UTC](https://meta.discourse.org/t/support-official-docker-packages-on-red-hat-centos/73476/1 "2017-11-05T20:05:39Z")

</div>

Docker is officially supported in RHEL/CentOS 7 in the _extras_ repository: [How is the docker container runtime supported in RHEL 7? - Red Hat Customer Portal](https://access.redhat.com/solutions/1408853)

They provide two different packages, `docker` (1.12.6) and `docker-latest` (1.13.1): [Introducing docker-latest for RHEL 7 and RHEL Atomic Host - Red Hat Customer Portal](https://access.redhat.com/articles/2317361)

As with everything included in the base distro, they are maintained by Red Hat and fixes are backported as necessary. Red Hat’s Docker packages are stable and used in production for their OpenShift Enterprise product.

However, the Discourse installer refuses to use them, since it does not know that they are Red Hat LTS version, which makes sense if you’re using the official Docker repository, but not with Red Hat’s packages. Installing the Docker 3rd party repository is unsupported by Red Hat, introduces an additional dependency and is and potentially less stable than using the Red Hat packages.

I can confirm that the Discourse cloud setup - with the version check commented out - works perfectly fine with CentOS 7.4 and `docker-latest` (1.13.1).

The Discourse installer should detect RHEL and do some basic RHEL-specific checks:

- we might want to check for ftype=0 on XFS, but it probably works fine even with ftype=0 set (many production OpenShift setups use ftype=0 without experiencing issues, as far as I know, it’s mostly about performance)
- either correct SELinux context set for Docker volumes or Docker configured without `--selinux-enabled` (by default, Red Hat’s Docker version uses SELinux sVirt as an additional layer of security against container escapes - it can be turned off without disabling SELinux for the whole system)

---

_[View the full topic](https://meta.discourse.org/t/support-official-docker-packages-on-red-hat-centos/73476)._