A: Currently, the only hypervisor that is supported is QEMU. We are obviously open to adding more support for other various hypervisors but there are considerations to be had.
A: Sure! We accept pull requests and if you have prior kernel experience please get in touch with NanoVMs - they might even want to pay you.
ops builds a disk image artifact that you can typically find (by default) in the same current working directory after you run an instance, as the filename "image". This is what is executed by
qemu to run your code or application.
A: Yes, it is possible to run
ops within a container such as docker. Although, it is NOT recommended to do so, especially for production environments. You will likely run into performance related issues.
A: We consider this an anti-pattern of software development and a scourge on the software ecosystem. It is advised to utilize your native language API and libraries to achieve the task instead.
A: The tool was originally addressed for transient services yet full fs functionality is on the way.
A: Yes, it is possible to setup bridged networking on various cloud providers, but it is recommended to run it on a physical linux server with an ethernet connection. In order to do so, you need to create a second network interface on the instance. Use one interface for the network bridge, and the other for your SSH connection.
Note: We are currently looking at providing native AWS and GCE support.
A: This also could happen on a cloud instance (AWS, digital ocean, google cloud) when there is only a single network interface.
You can bridge on a different interface than the one you are ssh'ing on to remedy this.
A: This could work with kubernetes but kubernetes is a container orchestrator and is typically deployed on top of an existing virtual machine whereas the intention for these are to run as virtual machines.