Re: Should we include docker support by default?
Pat Riehecky <[email protected]>
| Newsgroups | gmane.linux.redhat.anaconda.devel |
|---|---|
| Message-ID | <[email protected]> |
On 12/01/2015 07:23 PM, Brian C. Lane wrote: > I've been doing some experiments for bz#1283701, supporting running > docker at install time to pull down images without rebooting into the > system first. At first I thought it would be much harder than it is. > > I've added docker and some support libraries to lorax, they only added > about 12M and that's before I've even looked at trying to trim them down > at all. > > I have an experimental %post --nochroot that starts up docker, points to > the LVM thin pool (setup by kickstart, not docker-storage-setup), and > pulls down a couple simple images. It writes the config to the target > system and kills off docker. The only slightly odd part is bind mounting > /var/lib/docker to /mnt/sysimage/var/lib/docker so that everything it > writes ends up on the target system. > > I propose turning the %post hack into some kickstart commands for > setting up the storage, pulling images, and doing whatever other normal > setup things are needed. > > What do you think? Is this worth the extra 12M (or so) to add this? I'll confess this sounds a bit more like orchestration than installation to me. Any chance for an example use case? Pat