-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more kickstart sanity checks to livemedia-creator #79
Comments
Does this mean that an LVM configuration with lorax is not possible? i tried this:
and i always get "name already in use" i think due to the fact that lorax is addin a "disk / --size" somewhere, also the vmdk i try to build is much too small. Can i build an LVM based image? thanks |
Were you trying with --no-virt? And which image type? |
Sorry for my late reply, strange times... I'm calling the composer like this: what does the --no-virt do? could not find it in the documentation on https://weldr.io/lorax/composer-cli.html#build-an-image also how do i handle my changes to the kickstart file, they get overwritten by a upgrade or reinstall? i could not find the right way to define my custom kickstart file my biggest problem at the moment is that lorax adds a "disk / size=something" to the final kickstart which seems then to be used to define the size of the vmdk. but the size is far to small and does not take into account all the size definitions of the lvm partitions |
Oh, so you're using lorax-composer, that's a different thing that builds on top of livemedia-creator. You cannot control the partitioning at all when using lorax-composer. Neither of them parse the LVM commands when examining the kickstart, I'd forgotten about that in my previous reply, so this really won't work. |
lmc really only supportst part / --size= not autopart, lvm, or --grow, etc. lmc should catch these before trying to start anaconda.
The text was updated successfully, but these errors were encountered: