Update: Check out Acorn, the innovative web server appliance we demoed at CppCon. Built using Mana, the new C++ Web Application Framework for IncludeOS.
A live demo of Acorn can be found at acorn2.unofficial.includeos.io (sporadically unavailable)
IncludeOS is an includable, minimal unikernel operating system for C++ services running in the cloud. Starting a program with #include <os>
will literally include a tiny operating system into your service during link-time.
The build system will:
- link your service with the necessary OS objects into a single binary
- attach a boot loader
- combine everything into a self-contained bootable disk image, ready to run on almost any modern hypervisor.
IncludeOS is free software, with "no warranties or restrictions of any kind".
Note: IncludeOS is under active development. The public API should not be considered stable.
Build from bundle | |
---|---|
Master | |
Dev |
- Extreme memory footprint: A minimal bootable image, including bootloader, operating system components and a complete C++ standard library is currently 707K when optimized for size.
- KVM and VirtualBox support with full virtualization, using x86 hardware virtualization, available on any modern x86 CPUs). In principle IncludeOS should run on any x86 hardware platform, even on a physical x86 computer, given appropriate drivers. Officially, we develop for- and test on Linux KVM, which power the OpenStack IaaS cloud, and VirtualBox, which means that you can run your IncludeOS service on both Linux, Microsoft Windows and macOS.
- C++11/14 support
- Standard C library using newlib from Red Hat.
- Virtio Network driver with DMA. Virtio provides a highly efficient and widely supported I/O virtualization. We are working towards the new Virtio 1.0 OASIS standard
- A highly modular TCP/IP-stack.
A longer list of features and limitations is on the wiki feature list
By default the project is installed to /usr/local/includeos.
However, it is recommended to choose a custom location as well as select the compiler we want clang to find.
To do this we can edit ~/.bashrc (in the home folder), adding these lines at the end of the file:
export CC=/usr/bin/clang-3.8
export CXX=/usr/bin/clang++-3.8
export INCLUDEOS_PREFIX=<HOME FOLDER>/includeos
export PATH=$PATH:$INCLUDEOS_PREFIX/bin
This will also crucially make the boot program visible globally, so that you can simply run boot <myservice>
inside any service folder.
NOTE: The script will install packages and create a network bridge.
$ git clone https://github.com/hioa-cs/IncludeOS
$ cd IncludeOS
$ ./install.sh
The script will:
- Install the required dependencies:
curl make clang-3.8 nasm bridge-utils qemu
. - Create a network bridge called
bridge43
, for tap-networking. - Build IncludeOS with CMake:
- Download the latest binary release bundle from github together with the required git submodules.
- Unzip the bundle to the current build directory.
- Build several tools used with IncludeOS, including vmbuilder, which turns your service into a bootable image.
- Install everything in
$INCLUDEOS_PREFIX/includeos
(defaults to/usr/local
).
Configuration of your IncludeOS installation can be done inside build/
with ccmake ..
.
A successful setup enables you to build and run a virtual machine. Running:
$ ./test.sh
will build and run this example service.
More information is available on the wiki.
- Copy the ./seed/service directory to a convenient location like
~/your_service
. Then, just start implementing theService::start
function in theService
class, located in your_service/service.cpp (Very simple example provided). This function will be called once the OS is up and running. - Update the CMakeLists.txt to specify the name of your project, enable any needed drivers or plugins, etc.
Example:
$ cp -r seed/service ~/my_service
$ cd ~/my_service
$ emacs service.cpp
... add your code
$ mkdir build && cd build
$ cmake ..
$ make
$ boot my_service
Take a look at the examples and the tests. These all started out as copies of the same seed.
IncludeOS is being developed on GitHub. Create your own fork, send us a pull request, and chat with us on Gitter. Please read the Guidelines for Contributing to IncludeOS.
Important: Send your pull requests to the dev
branch. It is ok if your pull requests come from your master branch.
We want to adhere as much as possible to the ISO C++ Core Guidelines. When you find code in IncludeOS which doesn't adhere, please let us know in the issue tracker - or even better, fix it in your own fork and send us a pull-request.
We're trying to grow a Wiki, and some questions might already be answered here in the FAQ.
See the Wiki front page for a complete introduction, system overview, and more detailed guides.