On 04/20/2018 11:41 AM, Chad Tindel wrote: > Dusty- > > Unfortunately I had signed up for the digest so there's no way to reply, I > fixed that problem moving forward. > >> I not as familiar with packer. Does it run a kickstart install? > > No, it starts up an ec2 instance with a base AMI (ami-1690b173 in us-east-2 > in this case) and runs whatever commands and scripts you want it to run to > install things, change configs, etc. When it done it creates a new AMI from > that running instance.
yeah I'm not sure exactly, but it sounds like what you are doing should work. Does packer power off the instance before creating a new AMI out of the disk image? If you try to trace the steps that packer does on your own (manually) do you get the same result? > >> > 2.? How do I install docker-compose in a way that it will persist across >> > reboots given that "atomic install docker-compose" doesn't work? >> >> `rpm-ostree install <rpm-name> && reboot` should work. > > OK but I don't think there is an RPM for docker-compose. Usually you just > curl it to download as shown here: There is at least in Fedora/EPEL, though I can't say how out of date they are: https://apps.fedoraproject.org/packages/docker-compose > > https://docs.docker.com/compose/install/#install-compose > > So how to do that kind of install? The steps there for curling a file into /usr/local/bin/ should work. That directory is read/write. > > Thanks, > > Chad
