reynir/albatross
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
albatross/packaging/Linux
History
Reynir Björnsson e6eba35a97 Linux README: add comment about socket paths
2020-11-26 08:09:24 +01:00
..
albatross_console.service Systemd services depend on their sockets 2020-11-11 14:31:26 +01:00
albatross_console.socket Linux: Fix socket permissions 2020-11-24 14:41:56 +01:00
albatross_daemon.service Systemd services depend on their sockets 2020-11-11 14:31:26 +01:00
albatross_daemon.socket Linux: Fix socket permissions 2020-11-24 14:41:56 +01:00
albatross_log.service albatross_log.service: don't depend on albatross_console 2020-11-26 07:29:04 +01:00
albatross_log.socket Linux: Fix socket permissions 2020-11-24 14:41:56 +01:00
albatross_stat.service Systemd services depend on their sockets 2020-11-11 14:31:26 +01:00
albatross_stat.socket Linux: Fix socket permissions 2020-11-24 14:41:56 +01:00
install.sh Install .socket files 2020-11-11 13:54:06 +01:00
README.md Linux README: add comment about socket paths 2020-11-26 08:09:24 +01:00

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.

  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/.
  3. You need to build a binary with one of the tenders (solo5-hvt, solo5-spt) to deploy.
  4. See install.sh for commands required to deploy it.
  5. sudo journalctl -fu albatross'*'.service
  6. 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