Reynir Björnsson
33f7b6bcee
* Use systemd socket activation * Pass a new command line argument --systemd-socket-activation to the daemons if running on Linux * Install .socket files * Systemd services depend on their sockets * Implement sd_listen_fds in OCaml * Set FD_CLOEXEC in sd_listen_fds * README: add comment about socket paths * Linux systemd scripts: Rename albatross_stat -> albatross_stats |
||
---|---|---|
.. | ||
albatross_console.service | ||
albatross_console.socket | ||
albatross_daemon.service | ||
albatross_daemon.socket | ||
albatross_log.service | ||
albatross_log.socket | ||
albatross_stats.service | ||
albatross_stats.socket | ||
install.sh | ||
README.md |
systemd service scripts
these are preliminary and just here to let people play with solo5-spt
, the seccomp-enabled backend for Solo5 on Linux.
Note: The socket paths are hardcoded relative to the RuntimeDirectory (tmpdir).
If you modify Vmm_core.socket_path
you must modify the corresponding .socket
file(s) in this directory.
- You need to build the
albatross
tooling in this repository - To run unikernels, you need to build and install solo5-elftool and at least one of the tenders: solo5-hvt and solo5-spt. They can be installed somewhere in PATH or in /var/lib/albatross/.
- You need to build a binary with one of the tenders (solo5-hvt, solo5-spt) to deploy.
- See
install.sh
for commands required to deploy it. sudo journalctl -fu albatross'*'.service
- ideally, once the services are up and running, you would be able to issue this command to deploy a unikernel:
sudo albatross-client-local helloworld /path/to/hello_world.spt