You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Hi, We cannot start after shutting down the Firecracker microVM. Do Ignite restart and shutdown commands take effect for microvm?Can anyone help us, thanks!
Here are the steps performed
Create a firecracker microVM
execute command: ignite run weaveworks/ignite-amazonlinux --name micro-vm --cpus 2 --ssh --memory 4GB --size 10G
SSH enter microVM, then execute shutdown or reboot command
some error information like this: ERRO[0006] failed waiting for session to exit: wait: remote command exited without exit status or exit signal
Hi, thanks for reporting the issue. This was a known issue and was fixed in #735. It's not available in the released version of ignite yet. As a workaround, you can set the flag --runtime containerd for now.
We'll be releasing a new version soon which will have this fix.
Hi, thanks for reporting the issue. This was a known issue and was fixed in #735. It's not available in the released version of ignite yet. As a workaround, you can set the flag --runtime containerd for now.
We'll be releasing a new version soon which will have this fix.
Hi, We cannot start after shutting down the Firecracker microVM. Do Ignite restart and shutdown commands take effect for microvm?Can anyone help us, thanks!
Here are the steps performed
Create a firecracker microVM
execute command: ignite run weaveworks/ignite-amazonlinux --name micro-vm --cpus 2 --ssh --memory 4GB --size 10G
SSH enter microVM, then execute shutdown or reboot command
some error information like this: ERRO[0006] failed waiting for session to exit: wait: remote command exited without exit status or exit signal
Start microVM by command: ignite start micro-vm
FATA[0000] unknown runtime ""
The text was updated successfully, but these errors were encountered: