Elektrobit / flake-pilot

Registration/Control utility for applications launched through a runtime-engine, e.g containers
MIT License
9 stars 5 forks source link

Support pulling image from components #102

Closed schaefi closed 1 year ago

schaefi commented 1 year ago

So far pulling a firecracker image was limited to the KIWI kis image type. With this commit it's also possible to pull an image from it's components; rootfs, kernel and optional initrd. This allows for example to make use of the firecracker hosted CI images or any other rootfs image in combination with some kernel/initrd. During the pull of such an image there is also a check for the sci binary inside of the rootfs. If it does not exist it gets added to the rootfs such that the firecracker-pilot can work with it. This Fixes #99

schaefi commented 1 year ago

@m-kat with the change here the following becomes possible

flake-ctl firecracker pull \
    --rootfs https://s3.amazonaws.com/spec.ccfc.min/ci-artifacts/disks/x86_64/ubuntu-18.04.ext4 \
    --kernel https://s3.amazonaws.com/spec.ccfc.min/img/quickstart_guide/x86_64/kernels/vmlinux.bin \
    --name firecore 
flake-ctl firecracker register --app /home/ms/mybash --target /bin/bash --vm firecore --no-net

mybash

Requires the PR from here #101 to be applied

schaefi commented 1 year ago

@m-kat please note I'm shelling out for mount/umount and copy because they get called through sudo such that a normal user can perform the pull action and only discrete commands that requires root permissions are called through sudo. Thanks