Should we continue installing docker by default?

Stephen Gallagher sgallagh at
Tue Nov 17 20:54:41 UTC 2015

Hash: SHA1

Similar to my thread about the @server-hardware-support group, the
@container-management group also takes up a good chunk of space (38MB
above the minimal install) in the default Server install, as well as
including an additional available-by-default service.

Originally, we included Docker for its popularity and because Cockpit
and rolekit each had some support for operating with it. In F23 and
onwards, rolekit is capable of automatically-installing docker if it
is required to support a role, so having it installed by default is no
longer critical from that perspective.

This leaves Cockpit: one of Cockpit's more popular features is the
ability to manage Docker images and containers from the UI. Cockpit
has the ability to start Docker on the system if it's installed but
not running. I'd like to recommend that Cockpit also grow the
capability to install Docker if an administrator wants to use that
portion of the UI. This way, we can avoid installing it by default and
just deploy it automatically once an Administrator is interested in
using it.

As a side-note, I think this is a policy we should consider following
throughout Server: try to do lazy package installation whenever
possible. Much of our philosophy in rolekit, Cockpit and realmd is
around installing what we need only when we need it and an
administrator has made a clear decision to use it. We should try to
make that a consistent policy.
Version: GnuPG v2


More information about the server mailing list