fedora-atomic-dib's Introduction

Usage

To build the image:

INSTALL_DEPS=1 DIB_RELEASE=27 ./fedora_atomic_dib/setup.sh

INSTALL DEPS=1 installs all the required packages to run diskimage-builder. It is only necessary to include it the first time.

To boot into the image:

./fedora-atomic-dib/gencloudinitiso.sh
DIB_RELEASE=27 sudo -E ./fedora-atomic-dib/qemu.sh

Goal:

building Fedora Atomic 27 image
using diskimage-builder 2.12.2
on Centos 7

Result:

modified existing instructions for diskimage-builder 2.3.3 to build Fedora Atomic 25 image

Problems:

Still need to put selinux into permissive mode on grub config in order to successfully boot into the image.
Can't use the 'baremetal' element as fedora-atomic depends on vm element.
Can't use dracut-network/dracut-regenerate as fedora-atomic cleanup removes dracut (https://bugs.launchpad.net/magnum/+bug/1699771).
Have to manually specify kernel & initrd pattern for dracut-network/dracut-regenerate.
Specifying DIB_RELEASE=25 does not give you a fedora atomic 25 image (https://bugs.launchpad.net/magnum/+bug/1699766).

fedora-atomic-dib's People

Contributors

Watchers

fedora-atomic-dib's Issues

Error when trying to execute `ostree admin deploy`

Log of disk-image-create is attached:
dib-uuid27.log
Current behaviour:

error: opendir(ostree/repo): No such file or directory

Expected behaviour:
Run to completion!
Steps to replicate:
setup.sh

cannot access '//boot/ostree/fedora-atomic-/vmlinuz': No such file or directory

Steps to reproduce:

Set the following values:

export DIB_BAREMETAL_KERNEL_PATTERN='ostree/fedora-atomic-*/vmlinuz*'
export DIB_BAREMETAL_INITRD_PATTERN='ostree/fedora-atomic-*/initramfs-*'

Expected behaviour:

Run after 80-fedora-atomic image has been loaded.

Current behaviour:

Running before 80-fedora-atomic image has been loaded (from what I understand).

2018-03-27 15:10:29.298 | dib-run-parts 50-bootloader completed
2018-03-27 15:10:29.299 | dib-run-parts Running /tmp/in_target.d/finalise.d/50-dracut-regenerate
2018-03-27 15:10:29.405 | + dnf -v -y install cryptsetup
2018-03-27 15:10:33.906 | + '[' install == install ']'
2018-03-27 15:10:33.906 | + '[' dnf == dnf ']'
2018-03-27 15:10:33.906 | + dnf mark install cryptsetup
2018-03-27 15:10:34.320 | + dnf -v -y install lvm2
2018-03-27 15:10:41.228 | Running in chroot, ignoring request.
2018-03-27 15:10:41.682 | + '[' install == install ']'
2018-03-27 15:10:41.682 | + '[' dnf == dnf ']'
2018-03-27 15:10:41.682 | + dnf mark install lvm2
2018-03-27 15:10:42.049 | + set -eu
2018-03-27 15:10:42.049 | + set -o pipefail
2018-03-27 15:10:42.049 | + source /lib/diskimage-builder/img-functions
2018-03-27 15:10:42.049 | + select_boot_kernel_initrd /
2018-03-27 15:10:42.049 | + TARGET_ROOT=/
2018-03-27 15:10:42.049 | + BOOTDIR=//boot
2018-03-27 15:10:42.050 | + '[' -n 'ostree/fedora-atomic-*/vmlinuz*' -a -n 'ostree/fedora-atomic-*/initramfs-*' ']'
2018-03-27 15:10:42.051 | +++ eval ls -1rv '//boot/ostree/fedora-atomic-*/vmlinuz*'
2018-03-27 15:10:42.051 | ++++ ls -1rv '//boot/ostree/fedora-atomic-*/vmlinuz*'
2018-03-27 15:10:42.051 | +++ head -1
2018-03-27 15:10:42.052 | ls: cannot access '//boot/ostree/fedora-atomic-*/vmlinuz*': No such file or directory
2018-03-27 15:10:42.053 | ++ basename
2018-03-27 15:10:42.053 | basename: missing operand
2018-03-27 15:10:42.053 | Try 'basename --help' for more information.
2018-03-27 15:10:42.054 | + KERNEL=
2018-03-27 15:10:42.059 | Traceback (most recent call last):
2018-03-27 15:10:42.059 |   File "/tmp/in_target.d/finalise.d/50-dracut-regenerate", line 67, in <module>
2018-03-27 15:10:42.059 |     main()
2018-03-27 15:10:42.059 |   File "/tmp/in_target.d/finalise.d/50-dracut-regenerate", line 52, in main
2018-03-27 15:10:42.059 |     raise e
2018-03-27 15:10:42.059 | subprocess.CalledProcessError: Command '['select-boot-kernel-initrd']' returned non-zero exit status 1.