fedora-kickstarts/fedora-atomic-vagrant.ks

# Like the Atomic Host cloud image, but tuned for vagrant: enable the
# vagrant user, disable cloud-init.

%include fedora-atomic.ks

user --name=vagrant --password=vagrant
rootpw vagrant

# The addition of the net.ifnames=0 and biosdevnames=0 option ensures that
# even on VirtualBox virt, we get a primary network device with "eth0" as the name
# This simplifies things and allows a single disk image for both supported Vagrant
# platforms (virtualbox and kvm)
bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0"

%post --erroronfail

# Work around cloud-init being both disabled and enabled; need
# to refactor to a common base.
systemctl mask cloud-init cloud-init-local cloud-config cloud-final

# The inherited cloud %post locks the passwd, but we want it
# unlocked for vagrant, just like downstream.
passwd -u root

# Vagrant setup
sed -i 's,Defaults\\s*requiretty,Defaults !requiretty,' /etc/sudoers
echo 'vagrant ALL=NOPASSWD: ALL' > /etc/sudoers.d/vagrant-nopasswd
sed -i 's/.*UseDNS.*/UseDNS no/' /etc/ssh/sshd_config
mkdir -m 0700 -p ~vagrant/.ssh
cat > ~vagrant/.ssh/authorized_keys << EOKEYS
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key
EOKEYS
chmod 600 ~vagrant/.ssh/authorized_keys
chown -R vagrant:vagrant ~vagrant/.ssh/

%end
fedora-atomic-vagrant: Sync with CentOS Atomic SIG I'm trying to keep things in sync - this mostly ensures the root password is unlocked, and drops the `services` line that is useless because that's not how kickstart inheritance works. 2016-12-13 13:56:01 +00:00			`# Like the Atomic Host cloud image, but tuned for vagrant: enable the`
			`# vagrant user, disable cloud-init.`
fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00
remove cloud from atomic kickstarts and point at new repo location Signed-off-by: Dennis Gilmore <dennis@ausil.us> 2016-04-11 19:09:19 +00:00			`%include fedora-atomic.ks`
fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00
			`user --name=vagrant --password=vagrant`
cloud-atomic-vagrant: Set root's password to vagrant too This matches the Base box, and is standard per the Vagrant Base Box guidelines: http://docs.vagrantup.com/v2/boxes/base.html https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-May/msg00046.html 2015-05-13 21:33:07 +00:00			`rootpw vagrant`
fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00
Fix f23 vagrant atomic host not having eth0 net device name. Fixes https://fedorahosted.org/cloud/ticket/141 2015-12-09 16:36:17 +00:00			`# The addition of the net.ifnames=0 and biosdevnames=0 option ensures that`
			`# even on VirtualBox virt, we get a primary network device with "eth0" as the name`
			`# This simplifies things and allows a single disk image for both supported Vagrant`
			`# platforms (virtualbox and kvm)`
			`bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0"`

fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00			`%post --erroronfail`

			`# Work around cloud-init being both disabled and enabled; need`
			`# to refactor to a common base.`
atomic-vagrant: Mask cloud-init instead of using rm on /etc Now that cloud-init is enabled in the systemd unit, that change goes in /usr/lib...which we can't easily change. There are two potentially sane solutions: - Refactor the kickstarts here - Some support for systemd presets in kickstart files would allow us to have a later override here 2015-03-04 16:58:01 +00:00			`systemctl mask cloud-init cloud-init-local cloud-config cloud-final`
fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00
fedora-atomic-vagrant: Sync with CentOS Atomic SIG I'm trying to keep things in sync - this mostly ensures the root password is unlocked, and drops the `services` line that is useless because that's not how kickstart inheritance works. 2016-12-13 13:56:01 +00:00			`# The inherited cloud %post locks the passwd, but we want it`
			`# unlocked for vagrant, just like downstream.`
			`passwd -u root`

fedora-cloud-atomic-vagrant: New file for Changes/Vagrant_Box_Atomic See https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic 2015-02-25 22:26:42 +00:00			`# Vagrant setup`
			`sed -i 's,Defaults\\s*requiretty,Defaults !requiretty,' /etc/sudoers`
			`echo 'vagrant ALL=NOPASSWD: ALL' > /etc/sudoers.d/vagrant-nopasswd`
			`sed -i 's/.UseDNS./UseDNS no/' /etc/ssh/sshd_config`
			`mkdir -m 0700 -p ~vagrant/.ssh`
			`cat > ~vagrant/.ssh/authorized_keys << EOKEYS`
			`ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key`
			`EOKEYS`
			`chmod 600 ~vagrant/.ssh/authorized_keys`
			`chown -R vagrant:vagrant ~vagrant/.ssh/`

			`%end`