Minimum required Docker version and Docker versions available in offical package reqositories of Linux distributions

(Jens Pelzetter) #1


it would be very helpful if you could keep the minimum required version of Docker at the version(s) available in the official package repositories of the most used Linux Distributions. For example in Fedora 27 the Docker version available as official package is 1.13. The most current version of Discourse requires Docker version 17.03.1.

Also many admins might be unconformable with running bleeding edge distributions like Fedora or Ubuntu and prefer distributions like RHEL, CentOS or Debian…

Best regards


(Rafael dos Santos Silva) #2

We try to keep up with supported version from upstream, and the 1.13 version stopped receiving updates in 2017-03-01:

17.03.0-ce (2017-03-01)
IMPORTANT: Starting with this release, Docker is on a monthly release cycle and uses a new YY.MM versioning scheme to reflect this. Two channels are available: monthly and quarterly. Any given monthly release will only receive security and bugfixes until the next monthly release is available. Quarterly releases receive security and bugfixes for 4 months after initial release. This release includes bugfixes for 1.13.1 but there are no major feature additions and the API version stays the same. Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.

From a quick look, it looks Docker supports Fedora in the same way they do in Ubuntu, with official guide and repository: Get Docker CE for Fedora | Docker Documentation

Also, you can always pass the —skip-prereqs flag to the launcher script if you want.

(Matt Palmer) #3

I hear you on wanting to stick to distro-provided stuff, even on stable releases (and I’m a Debian guy…), but here’s the thing with Docker: old releases are terrible. The software is immature, bug-ridden, feature-incomplete, and generally a massive pain in the posterior. It doesn’t get better over time, but it’s at least different. The only way to get within shouting distance of sanity is to track the upstream releases. It still doesn’t guarantee (or even give reasonable confidence of) success or stability, but trying to maintain compatibility within our tooling for older versions of Docker isn’t feasible with the size of the team we have, so we’ve decided to require recent Docker versions, and damn the torpedoes. The only saving grace is that Docker provides reasonably non-sucky packages of the current releases for most distros (including RHEL, CentOS, and Debian).