On Friday, March 11, 2016 9:58:54 AM CST Chris Murphy wrote:
Hi,
The installer autopart in Cloud Atomic ISO leaves a bunch of free
space in the VG, which on first boot is turned into a dm thin pool by
docker-storage-setup. This is quite cool, so I'm suggesting it for
Server (minus the auto configuration part), but I can't tell where the
code is that alters the installer's autopartitioning behavior. The
kickstart file says it's using autopart, it doesn't have a breakdown
of what it's asking the installer to do, so I guess by virtue of it
being a Cloud productized installer it knows to do this.
Suggestions?
The code that overrides anaconda's defaults lives in fedora-productimg-atomic
Dennis