leigh capili

Thanks for confirming on recent versions of ignite @kobayashi. I think this issue may be related to firecracker's special handling of os `reboots`. If I recall correctly, reboots simply shutdown...

Containerd lifecycle is still failing with the most recent network lifecycle change. (c17a99c7bbff8b9d1e96594e5f6356de61bb98fd) On the ignite dev call, we discussed checking in some e2e tests with the goal of fixing...

@luxas and @bboreham are currently pairing on a macvlan implementation. Some of the bits and pieces are working. The tricky bits here are how the network namespace and device nodes...

This feature is not yet supported by firecracker, but they do have a roadmap issue for it: https://github.com/firecracker-microvm/firecracker/issues/1184 Ignite is dependent on firecracker for support of hardware/virt level features such...

I'm curious about your use-case here. Ignite makes it possible to bake properly pre-configured images and re-create fresh VM's quickly. How would you want to use snapshots or imagine how...

Notable that k8s api machinery dictates labels be dns-1123 subdomains. That means that labels should be small and in a fairly restricted schema that should be compatible with most or...

@rugwirobaker, What exactly is the misconfiguration? Is your vm missing an `/etc/resolv.conf` like this command implies? - Test for Empty /etc/resolv.conf `[ -s /etc/resolv.conf ] || echo '/etc/resolv.conf is empty'`...

I'm guessing your host's nameserver is the GCP metadata server `169.254.169.254` Cloud DNS reference: https://cloud.google.com/dns/docs/overview#vpc-name-resolution-order I'm surprised there is no `/etc/resolve.conf` in your guest vm's. Your `/run/systemd/resolve/resolv.conf` should be equal...

@rugwirobaker You can't escape the vm into the wrapper-container. You can use the `ctr` or `docker` command line tools from the host to exec in depending on your runtime: ```...

This could be related to and potentially fixed by #581