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
14 lines
1,014 B
Markdown
14 lines
1,014 B
Markdown
# systemd service scripts
|
|
|
|
these are preliminary and just here to let people play with `solo5-spt`, the seccomp-enabled backend for [Solo5](https://github.com/Solo5/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.
|
|
|
|
1) You need to build the `albatross` tooling in this repository
|
|
2) 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/.
|
|
2) You need to build a binary with one of the tenders (solo5-hvt, solo5-spt) to deploy.
|
|
3) See [`install.sh`](./install.sh) for commands required to deploy it.
|
|
4) `sudo journalctl -fu albatross'*'.service`
|
|
5) 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`
|