1. Manuals
  2. Tumbleweed
  3. flake-pilot-firecracker
  4. flake-ctl-firecracker-pull(8)

Scroll to navigation

FLAKE-CTL-FIRECRACKER-PULL(8)() FLAKE-CTL-FIRECRACKER-PULL(8)()

NAME

FLAKE-CTL-FIRECRACKER-PULL(8) -

NAME

flake-ctl firecracker pull - Fetch firecracker image

SYNOPSIS

USAGE:


    flake-ctl firecracker pull [OPTIONS] --name <NAME> <--kis-image <KIS_IMAGE>|--rootfs <ROOTFS>|--kernel <KERNEL>>
OPTIONS:


    --force


    --initrd <INITRD>


    --kernel <KERNEL>


    --kis-image <KIS_IMAGE>


    --name <NAME>


    --rootfs <ROOTFS>


DESCRIPTION

Pull the components of a firecracker image from the given location into /var/lib/firecracker/images/NAME on the local machine. After completion the available firecracker images can be listed via:

$ tree /var/lib/firecracker/images


and shows a file structure like in the following example

/var/lib/firecracker/images
└── myImage


     ├── initrd


     ├── kernel


     └── rootfs


OPTIONS

Force pulling the image even if it already exists This will wipe existing data for the provided identifier
Single initrd image to pull into local image store
Single kernel image to pull into local image store
Firecracker image built by KIWI as kis image type to pull into local image store. This means the file behind KIS_IMAGE is expected to be a tarball containing the KIS components; rootfs-image, kernel and optional initrd
Image name used as local identifier
Single rootfs image to pull into local image store

EXAMPLE

$ flake-ctl firecracker pull --name myImage --kis-image \


    https://download.opensuse.org/repositories/home:/marcus.schaefer:/delta_containers/images/firecracker-basesystem.x86_64.tar.xz
$ flake-ctl firecracker pull --name firecore \


    --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


AUTHOR

Marcus Schäfer

COPYRIGHT

(c) 2022, Elektrobit Automotive GmbH (c) 2023, Marcus Schäfer