chromium headless unikernel

[rgarcia]

Headless chromium image!

Main features:

• Runnable as a docker image (./{build,run}-docker.sh) for local testing
• Unikernel build (./{build,run}-unikernel.sh) uses erofs for max resource efficiency (erofs == memory on demand, cpio == first allocate all in memory, then use)
• some test scripts:
  • cdp-test: python script that you can feed the url of the docker image or the unikernel instance and it will figure out hte debugger URL and run a basic test
  • uk-check-stats.sh: polls the unikraft API for memory, CPU, and network usage data for an instance. Useful for figuring out what the memory allocation should be

[Sayan-]

just to confirm: this difference from the headful image is due to requirements for erofs?

[rgarcia]

yeah this is how the final filesystem for the vm is constructed. In the headful image we use kraft's built in support for Dockerfiles but that doesn't use erofs. So here we use the Dockerfile "by hand" and construct the root fs for the VM, and then reference that folder in the Kraftfile