On 03/11/2016 01:54 PM, Chris Murphy wrote:
On Fri, Mar 11, 2016 at 11:07 AM, Stephen Gallagher
<sgallagh(a)redhat.com> wrote:
> What does docker-storage-setup do if there are multiple VGs on the system? Does
> it just pick one and use that, or does it take over them all?
Ok this was faster than even considering looking for a stick...
https://github.com/projectatomic/docker-storage-setup/blob/master/docker-...
FWIW, this file doesn't exist on my Fedora Server system anywhere. I wonder if
this isn't in a released version yet. If it's not, then what I'm going to say
below may not be relevant... yet.
# The volume group to use for docker storage. Defaults to the
# volume group where the root filesystem resides. If VG is specified and the
# volume group does not exist, it will be created (which requires that "DEVS"
# be nonempty, since we don't currently support putting a second partition on
# the root disk).
#
# VG=
So yeah, this will take some adjustment because you really don't want
it taking up free extents in this VG. Create a new VG, move a specific
amount of extents, change the .conf file to explicitly specify the VG
to use, and then docker-storage-setup can safely run.
I don't think we necessarily need to go this far. I mean, the
docker-storage-setup.conf strongly implies that it will use 40% of the available
free space (or 2GiB, whichever is larger, I'm guessing) and leave the rest
alone. I think that's probably not unreasonable to just leave as-is if we go the
route of leaving most of the space free.
I guess if we wanted to be picky, we could always ship a modified version that
limits us to 20% or something, but I think we're splitting hairs at that point.
So in general, I think we could probably opt for modifying the Server productimg
package to drop the separate /home partition and instead create a single /
partition with a minimum size of 2GiB and a maximum size of ??? (help me out
here) and then just leave the rest empty.
That said, in a server environment there may be a decent argument for having
/var on a separate partition by default, if only so that out of control logs
don't fill up the system partition.
After installation, Cockpit can be used to resize the system (and/or /var)
partition if needed.