-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quark builder #3
Comments
What should we use for the following?
|
How do we have to get the kaps (old run0) binary ? |
You'd build it from source. |
https://github.com/virt-do/lab/tree/main/do-vmm could be a good starting point. |
Hey @sameo, i don't understand what you're expecting from "a kernel command line" in : |
Hey @leofvo . This is the set of kernel parameters that you pass to a kernel when booting it. This is our default kernel command line, but this is something that should be configurable. So quark.json should have a field containing that command line, and that's a string. Does that make sense? See https://www.freedesktop.org/software/systemd/man/kernel-command-line.html as well. |
Hi @sameo, about the kernel command line contained in the quark.json file, should it be configurable with the CLI when building a quardle ? Therefore, would it be useful to let the user state his own If not, all the config (kernel & initrd file names, kernel cli) should be hard-coded ? Am I right ? |
The
quark
builder is a CLI tool for building images forlumper
to boot.Those images will be made of:
a. A
run0
binaryb. A container image
The output of the builder will be a
quark
bundle, i.e. aquardle
.A
quardle
is a compressed tarball (tar gz
) made of a kernel, an initrd and a config file (quark.json
).quark.json
must at least contain the kernel and initrd file names, a kernel command line and the container URL.CLI
Building a
quardle
with the container image bundled into the initramfs image:Building a
quardle
with the container image to be pulled from within the guest:Output
The above command will generate
quardle_name.qrk
The text was updated successfully, but these errors were encountered: