Am 18.11.2015 um 15:55 schrieb Miloslav Trmac:
2015-11-17 21:54 GMT+01:00 Stephen Gallagher <sgallagh(a)redhat.com
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.
As a side-note, I think this is a policy we should consider following
throughout Server: try to do lazy package installation whenever
So I am vaguely worried about this trend. Should image size really the
yes in case of a default setup
Functionality added by default, and especially as mandatory, on top
minimal install (whatever minimal install is this year), is not just
useful the way a new feature is useful in an appliance; it is also (and
IMO primarily) useful as making the “platform” more valuable because
application writers can depend on the feature being always available,
and users can expect the applications to be more easily deployed.
where do you draw the line?
if you have 100, 200, 300 server instances size matters and if you open
the candle of worms "what *could* be useful" you end in fat default
installs to satisfy anybody
it's way easier to install something you need then get rid of things you
don't know why they are there from the start
Docker is a good example: its users are not rolekit and Cockpit, its
users are all the Dockerized applications out there; and/if/ Docker
succeeds as an application delivery mechanism, its value to all the
other applications will be much larger than the value of making rolekit
and Cockpit a bit easier to deploy
no docker is a bad example, we are running Fedora servers from 2008 on
for everything virtualized, long before "cloud" and "docker" and while
you can indeed run docker inside a virtual machine none of them do and
will in the near future