As we add/remove/change behavior and make doc changes, the documentation reflects the committed code, but not the released code.

We've seen multiple occurrences of users trying to unsuccessfully configure/use the latest released firecracker binary following documentation which is no longer applicable.

Options to keep binary and docs in sync:

1. Have separate branches release and `deve

Eclipse OMR is a C/C++ toolkit for building language runtimes. OMR has a high level JIT compilation library called JitBuilder, which is built on OMR's more general compilation framework. We also have a demo VM called [Base9](https://github.com/b9org/

I tried running the instructions for a START1-M instance at Scaleway

$ qemu-img create -f qcow2 MyDisk.qcow2 64G

Command 'qemu-img' not found, but can be installed with:

sudo apt install qemu-utils

Also, the KVM prerequisite can be installed and configured as de

Description of problem

Following the installation guide for minikube, at least with a certain configuration, results in a test pod stuck in ContainerCreating.

psnively@oryx-pro:~|⇒  cd packaging/kata-deploy 
psnively@oryx-pro:~/packaging/kata-deploy|master 
⇒  minikube delete
! "minikube" cluster does not exist
! "minikube" profile does not exist
psnively@oryx-pro:~/packag

The documentation for ProcessControlBlock::acquire_heap is reentrant. This code seems to use the rust std Mutex, which is not.

https://github.com/lumen/lumen/blob/aeae1721d0fc02982898c8bcd1e7ed0ae5db151c/liblumen_alloc/src/erts/process.rs#L202-L204

This causes issues when (for instance) using ProcessControlBlock::tuple_from_iter along with an iterator that allocates.

Using the following YAML should output warnings per offending spec instead of ignoring them silently.
Example:

footloose create
WARN[0000] Options under "spec.ignite" for "manager-%d" are ignored when using the "docker" backend
WARN[0000] Options under "spec.ignite" for "worker-%d" are ignored when using the "docker" backend
INFO[0000] Docker Image: quay.io/footloose/ubuntu18.04 prese

Some old programs versions can be found here if someone needs them to test old exploits for instance.

On Fedora systems, the default user is in the wheel group. If multipass would prefer that ahead of the "adm" group, then immediately after installing the snap multipass would work without any additional configuration.

Is your feature request related to a problem? Please describe.
The current documentation of LIKO-12 suffers from many problems, including:

• Generated on the user's browser, and so it's not indexable by search engines.
• It's hard to navigate between pages.
• The theme is not much good.

Describe the solution you'd like
We want a better documentation software, which:

• Stores the d

The Agent version field in the cc-env output...

$ cc-runtime cc-env|grep -A 2 Agent
[Agent]
  Type = "hyperstart"
  Version = "<<unknown>>"

... is always <<unknown>> as there is no clean way to query it.

This could be done using losetup + mount, but for now atleast we're putting that functionality into the collect script (see #1055).

Remove Agent.Version from t