liquidmetal-dev / liquidmetal-dev/flintlock

Working example

Open
#811 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
1.5k
Forks
73
Avg merge
17h 24m
Merged PRs (30d)
30

Description

Hi. I'm struggling to get up and running with flintlock. The documentation has led me through all steps, I can see stdout of my firecraker instances via /var/lib/flintlock/vm/ns1/mvm1/01HN0B.... . however, I struggle to get a working json config. the provided https://github.com/weaveworks-liquidmetal/flintlock/blob/main/hack/scripts/payload/CreateMicroVM.json links a docker container that's 404, the provided images (capmvm-kubernetes:1.23.5) from the docs, with the rest of the configuration taken from CreateMicroVM.json , lead to systemd errors (dbus not found) and netplan apply fails, so my vm is offline, I also do not know how to connect to it via the console.

Seeing the same with the hammertime example.json

> [ 0.000000] Linux version 5.10.77 (root@cd4feae7407d) (gcc (Ubuntu 7.5.0-6ubuntu2) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP Tue Jan 17 16:03:24 UTC 2023
> [ 0.000000] Command line: i8042.noaux i8042.dumbkbd network-config=dmVyc2lvbjogMgpldGhlcm5ldHM6CiAgZXRoMDoKICAgIG1hdGNoOgogICAgICBtYWNhZGRyZXNzOiBBQTpGRjowMDowMDowMDowMQogICAgYWRkcmVzc2VzOgogIC
> AgLSAxNjkuMjU0LjAuMS8xNgogICAgZGhjcDQ6IGZhbHNlCiAgICBkaGNwNjogZmFsc2UKICAgIGRoY3AtaWRlbnRpZmllcjogbWFjCiAgZXRoMToKICAgIG1hdGNoOgogICAgICBtYWNhZGRyZXNzOiAxQToyRToyMTo3ODpEQjpBMgogICAgZGhjcDQ6IHRydW
> UKICAgIGRoY3A2OiB0cnVlCiAgICBkaGNwLWlkZW50aWZpZXI6IG1hYwo= ds=nocloud-net;s=http://169.254.169.254/latest/ console=ttyS0 reboot=k panic=1 pci=off i8042.nomux i8042.nopnp root=/dev/vda rw virtio_mm
> io.device=4K@0xd0001000:5 virtio_mmio.device=4K@0xd0002000:6 virtio_mmio.device=4K@0xd0003000:7 virtio_mmio.device=4K@0xd0004000:8
> ...
> SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.33: No such file or directory
> [ 0.502267] systemd[1]: Failed to look up module alias 'autofs4': Function not implemented
> [ 0.508993] systemd[1]: systemd 245.4-4ubuntu3.19 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKI
> D +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
> ...
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> ...
> [ 12.266186] cloud-init[913]: 2024-01-25 13:35:43,876 - activators.py[WARNING]: Running ['netplan', 'apply'] resulted in stderr output: Failed to connect system bus: No such file or directory
>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with hack/scripts/payload/CreateMicroVM.json and the hammertime example.json, then compare their referenced images and configuration with the supplied boot logs. Done means a documented JSON configuration starts a working VM with networking, and the documentation explains how to connect through the console.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation, networking
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.