ignite icon indicating copy to clipboard operation
ignite copied to clipboard

Ignite a Firecracker microVM

Results 124 ignite issues
Sort by recently updated
recently updated
newest added

When running: ``` sudo ignite --log-level debug run curx/ignite-debian:10 \ --cpus 2 \ --memory 1GB \ --ssh \ --name my-vm ``` I always get: ```FATA[0000] ambiguous kernel query: "weaveworks/ignite-kernel:4.19.125" matched...

Is the snapshooting feature active in Ignite?

kind/feature
area/runtime

I have an ignite host that's routinely hanging under load. Host becomes completely unresponsive, doesn't ping, SSH connections freeze and time out, no messages on ipmi console. Ubuntu 20.04. AMD...

A pre-flight check prevents Ignite to start a vm (`strings` not found in PATH) https://github.com/weaveworks/wks-quickstart-firekube/issues/90

Using a Debian 10/buster VM running under WSL2 here : ``` root@DESKTOP-G37QQGG:~/ignite# cat test-vm.yaml apiVersion: ignite.weave.works/v1alpha1 kind: VM metadata: name: test-vm spec: image: ociClaim: ref: weaveworks/ignite-ubuntu cpus: 2 diskSize: 3GB...

kind/feature
documentation/improvement
kind/support
area/runtime

ignite fails to start second ignite vm in ubuntu 20.04 running as a KVM guest os. It hangs. The first microvm runs with no issues. See below error message: ```...

All missing validation functions are tracked here. If you find some validation missing, add it to this list or comment on this issue. - [ ] VM CPUs - [...

good first issue
priority/backlog
kind/enhancement

If you are in the `ignite-spawn` container, you have root and can change host files like `/etc/resolv.conf` using ignite `

kind/bug
help wanted
good first issue
area/security
priority/important-soon
area/runtime
hacktoberfest

It would be nice if one could run a command like: `ignite ps --format "table {{.ID}}\t{{.Mounts}}"` Similar to Docker's ps: `docker ps --format "table {{.ID}}\t{{.Mounts}}"`

kind/feature
help wanted
good first issue
area/UX
priority/backlog

Would be really nice if terminal resizes after `ignite ssh` or `ignite exec` started got propogated down the SSH connection. I guess https://github.com/weaveworks/ignite/blob/5da6ea4100dbef5b49ee86229bc7981a696fb60b/cmd/ignite/run/ssh.go#L128-L132 has something to do with this.