Compare commits

...

15 Commits
0.28.1 ... f28

Author SHA1 Message Date
Kevin Fenzi
b3e9d978c7 Revert "Use the fedora-release-container package to get the release version"
This reverts commit ab0f96678e.

Fedora 28 does not have a fedora-release-container, so this makes it fail.
2019-03-26 11:58:15 -07:00
Clement Verna
ab0f96678e Use the fedora-release-container package to get the release version
Signed-off-by: Clement Verna <cverna@tutanota.com>
2019-02-05 16:02:01 +01:00
Clement Verna
d8c1268e61 Use coreutils instead of coreutils-single in containers.
Fixes https://github.com/fedora-cloud/docker-brew-fedora/issues/58

Signed-off-by: Clement Verna <cverna@tutanota.com>
2018-11-02 19:38:08 +01:00
Clement Verna
a600dd769e Containers do not need grubby.
Make sure that we do not install grubby on the
container base image.
https://pagure.io/releng/issue/7872

Signed-off-by: Clement Verna <cverna@tutanota.com>
2018-10-30 20:30:55 +01:00
Joe Doss
c3841ff35a Revert "Remove -NetworkManager to fix BZ#1596062"
This reverts commit d95b59ac3b.
2018-07-12 15:33:14 -05:00
Joe Doss
d95b59ac3b Remove -NetworkManager to fix BZ#1596062 2018-07-12 14:43:44 -05:00
Dusty Mabe
9109d36075 atomic: make url match ostreesetup line
When we reset the origin to think it came from another branch, let's
use the same URL as we used in the ostreesetup line.

Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
2018-06-18 13:56:54 -04:00
Peter Robinson
1a55167415 Merge #400 Run Initial Setup in reconfig mode on IoT images 2018-05-30 09:03:36 +00:00
Martin Kolman
5f1ff6c079 Run Initial Setup in reconfig mode on IoT images
Use the "firstboot --reconfig --enable" command[0] to tell
Initial Setup that it should run in the reconfig mode.

[0] http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#firstboot
2018-05-29 16:16:45 +02:00
Peter Robinson
7e9f7558eb IoT: add firstboot line to ensure we get all initial-setup spokes
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2018-05-29 15:09:37 +01:00
Peter Robinson
3721df6e5a IoT: move to simple partitioning 2018-05-28 12:49:10 +01:00
Peter Robinson
2f5861cb1c IoT: enable rngd, fix AMA0 console, blacklist vc4 driver (for the moment)
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2018-05-11 14:32:57 +01:00
Peter Robinson
8ca87ecf8d IoT: update ostree URLs 2018-05-08 17:50:56 +01:00
Peter Robinson
f1eae2ab45 initial Fedora IoT kickstart
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2018-05-08 12:56:50 +01:00
Stephen Gallagher
ec4546fbb4 Add hardware and network support groups to aarch64 server (#1569183)
These groups were added to the server environment group in comps
but the change was not mirrored here, so the ARM server disk
image is still missing wifi support etc.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
2018-04-25 17:54:09 -04:00
4 changed files with 128 additions and 3 deletions

View File

@@ -68,7 +68,7 @@ arch=$(uname -m)
# Set the origin to the "main ref", distinct from /updates/ which is where bodhi writes.
# We want consumers of this image to track the two week releases.
ostree admin set-origin --index 0 fedora-atomic https://kojipkgs.fedoraproject.org/atomic/28/ "fedora/28/${arch}/atomic-host"
ostree admin set-origin --index 0 fedora-atomic https://kojipkgs.fedoraproject.org/compose/atomic/repo/ "fedora/28/${arch}/atomic-host"
# Make sure the ref we're supposedly sitting on (according
# to the updated origin) exists.

View File

@@ -5,10 +5,13 @@ services --enabled=sshd,NetworkManager,chronyd,initial-setup
autopart
%packages
# install the default groups for the server evironment since installing the environment is not working
# install the default groups for the server environment since installing the environment is not working
@server-product
@standard
@headless-management
@hardware-support
@networkmanager-submodules
@container-management
@domain-client
-initial-setup-gui

View File

@@ -32,7 +32,7 @@ autopart --noboot --nohome --noswap --nolvm
%packages --excludedocs --instLangs=en --nocore
fedora-release
bash
coreutils-single
coreutils
glibc-minimal-langpack
libcrypt
rpm
@@ -49,6 +49,7 @@ util-linux
-shared-mime-info
-trousers
-xkeyboard-config
-grubby
%end

121
fedora-iot.ks Normal file
View File

@@ -0,0 +1,121 @@
# This is the kickstart for Fedora IoT disk images.
text # don't use cmdline -- https://github.com/rhinstaller/anaconda/issues/931
lang en_US.UTF-8
keyboard us
timezone --utc Etc/UTC
auth --useshadow --passalgo=sha512
selinux --enforcing
rootpw --lock --iscrypted locked
firstboot --reconfig --enable
# Add most common consoles console=ttyAMA0 console=ttyS0 console=ttyS1 as kernel boot parameter
bootloader --timeout=1 --append="console=tty1 console=ttyS0,115200n8 console=ttyS1,115200n8 console=ttyAMA0,115200n8 net.ifnames=0 modprobe.blacklist=vc4"
network --bootproto=dhcp --device=link --activate --onboot=on
services --enabled=NetworkManager,sshd,rngd,initial-setup
# tell Initial Setup to run in the reconfig mode
firstboot --reconfig --enable
zerombr
clearpart --all
autopart --nohome --noswap --type=plain
# Equivalent of %include fedora-repo.ks
# Pull from the ostree repo that was created during the compose
ostreesetup --nogpg --osname=fedora-iot --remote=fedora-iot --url=https://kojipkgs.fedoraproject.org/compose/iot/repo/ --ref=fedora/28/${basearch}/iot
reboot
%post --erroronfail
# Find the architecture we are on
arch=$(uname -m)
# Setup Raspberry Pi firmware
if [[ $arch == "aarch64" ]] || [[ $arch == "armv7l" ]]; then
cp -Pr /usr/share/bcm283x-firmware/* /boot/efi/
if [[ $arch == "aarch64" ]]; then
mv -f /boot/efi/config-64.txt /boot/efi/config.txt
cp -P /usr/share/uboot/rpi_3/u-boot.bin /boot/efi/rpi3-u-boot.bin
else
cp -P /usr/share/uboot/rpi_2/u-boot.bin /boot/fw/rpi2-u-boot.bin
cp -P /usr/share/uboot/rpi_3_32b/u-boot.bin /boot/fw/rpi3-u-boot.bin
fi
fi
# Set the origin to the "main ref", distinct from /updates/ which is where bodhi writes.
# We want consumers of this image to track the two week releases.
ostree admin set-origin --index 0 fedora-iot https://kojipkgs.fedoraproject.org/iot/28/ "fedora/28/${arch}/iot"
# Make sure the ref we're supposedly sitting on (according
# to the updated origin) exists.
ostree refs "fedora-iot:fedora/28/${arch}/iot" --create "fedora-iot:fedora/28/${arch}/iot"
# Remove the old ref so that the commit eventually gets cleaned up.
ostree refs "fedora-iot:fedora/28/${arch}/iot" --delete
# delete/add the remote with new options to enable gpg verification
# and to point them at the cdn url
ostree remote delete fedora-iot
ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary fedora-iot 'https://dl.fedoraproject.org/iot/repo/'
# older versions of livecd-tools do not follow "rootpw --lock" line above
# https://bugzilla.redhat.com/show_bug.cgi?id=964299
passwd -l root
# Work around https://bugzilla.redhat.com/show_bug.cgi?id=1193590
cp /etc/skel/.bash* /var/roothome
echo -n "Network fixes"
# initscripts don't like this file to be missing.
cat > /etc/sysconfig/network << EOF
NETWORKING=yes
NOZEROCONF=yes
EOF
# Remove any persistent NIC rules generated by udev
rm -vf /etc/udev/rules.d/*persistent-net*.rules
# And ensure that we will do DHCP on eth0 on startup
cat > /etc/sysconfig/network-scripts/ifcfg-eth0 << EOF
DEVICE="eth0"
BOOTPROTO="dhcp"
ONBOOT="yes"
TYPE="Ethernet"
PERSISTENT_DHCLIENT="yes"
EOF
echo "Removing random-seed so it's not the same in every image."
rm -f /var/lib/systemd/random-seed
echo "Packages within this iot image:"
echo "-----------------------------------------------------------------------"
rpm -qa
echo "-----------------------------------------------------------------------"
# Note that running rpm recreates the rpm db files which aren't needed/wanted
rm -f /var/lib/rpm/__db*
echo "Zeroing out empty space."
# This forces the filesystem to reclaim space from deleted files
dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
rm -f /var/tmp/zeros
echo "(Don't worry -- that out-of-space error was expected.)"
# For trac ticket https://pagure.io/atomic-wg/issue/128
rm -f /etc/sysconfig/network-scripts/ifcfg-ens3
echo "Adding Developer Mode GRUB2 menu item."
/usr/libexec/atomic-devmode/bootentry add
# Disable network service here, as doing it in the services line
# fails due to RHBZ #1369794
/sbin/chkconfig network off
# Anaconda is writing an /etc/resolv.conf from the install environment.
# The system should start out with an empty file, otherwise cloud-init
# will try to use this information and may error:
# https://bugs.launchpad.net/cloud-init/+bug/1670052
truncate -s 0 /etc/resolv.conf
%end