2018-04-02 17:34:28 +03:00
|
|
|
# linuxkit-builder
|
|
|
|
|
|
2018-07-13 16:41:06 +03:00
|
|
|
## Installation
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-07-13 16:41:06 +03:00
|
|
|
Fetch it from the NixOS binary cache:
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-07-13 16:41:06 +03:00
|
|
|
nix-store -r /nix/store/1f5zgx8qykz2fxzhqphmsfp6cvpnfc94-linuxkit-builder
|
|
|
|
|
nix-env -i /nix/store/1f5zgx8qykz2fxzhqphmsfp6cvpnfc94-linuxkit-builder
|
|
|
|
|
nix-linuxkit-configure
|
|
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
It'll write to:
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
- ~/.cache/nix-linuxkit-builder/, in particular
|
|
|
|
|
~/.cache/nix-linuxkit-builder/nix-state/console-ring is interesting
|
|
|
|
|
- ~root/.ssh/ for the SSH config
|
|
|
|
|
- /etc/nix/machines
|
|
|
|
|
- ~/Library/LaunchAgents/org.nix-community.linuxkit-builder.plist
|
2018-04-11 15:48:41 +03:00
|
|
|
|
|
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
It should automatically start and stay running, but ...
|
2018-04-11 15:48:41 +03:00
|
|
|
|
|
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
You can force start it with:
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
launchctl start org.nix-community.linuxkit-builder
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
You can force stop it with:
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
launchctl stop org.nix-community.linuxkit-builder
|
2018-04-11 15:48:41 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
If after you stop it you may want to check for processes, like:
|
2018-04-02 17:34:28 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
pgrep vpnkit
|
|
|
|
|
pgrep linuxkit
|
|
|
|
|
pgrep hyperkit
|
2018-04-02 17:34:28 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
If something goes wrong and it didn't stop propery, you can try:
|
2018-04-02 17:34:28 +03:00
|
|
|
|
2018-05-24 18:20:16 +03:00
|
|
|
pkill -F ~/.cache/nix-linuxkit-builder/nix-state/hyperkit.pid hyperkit
|
