[PATCH 3/3 rhel7-branch] atomic: set up atomic specific partitioning defaults
Colin Walters
walters at verbum.org
Tue Nov 4 17:52:09 UTC 2014
On Thu, Oct 23, 2014, at 11:33 AM, Brian C. Lane wrote:
> Note, it isn't always online, it pulls it from the same place it finds
> squashfs.img
So I think what we want then is lorax --with-product=/path/to/my/product.img and then lorax could inject around line 302, just after rb.create_runtime() ?
> My point in the previous message was that it looks like every user of
> docker is going to have their own ideas about how their host is setup,
> how to divide up storage, how to name things, use thinp or btrfs, etc.
Regardless of the options, there still needs to be a default. And for Atomic that default will be different from mainline (at least as long as mainline is LVM based).
thinp is orthogonal to this, could apply to both.
Also, as a downstream maintainer, while we offer multiple options we really want to encourage a secure and reasonably performant default, and at the moment that's dedicated LVM space. The Docker BTRFS is currently incompatible with SELinux, so is not suitable for a default.
> These are the things that kickstart excels at, letting the admin decide.
> From what I've read so far it looks like any kind of docker autopart we
> decided to implement would be wrong for a significant number of users,
> which makes it better to just teach them how to use kickstart commands
> to get what they want.
Agree that kickstart should be flexible. But my primary concern is with the interactive installation defaults.
More information about the anaconda-patches
mailing list