Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2017-10-24 16:47:04
Size: 897
Comment:
Revision 3 as of 2017-10-25 03:15:14
Size: 985
Editor: PaulWise
Comment: bug fixed, remove workaround
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
# workaround for #862758
root@FreedomBox:~# apt-get install -y gir1.2-nm-1.0
Line 26: Line 23:
root@FreedomBox:~# halt root@FreedomBox:~# ^D
Line 32: Line 29:

# To stop the container, either issue:
$ sudo machinectl stop FreedomBox

# or log in and run "halt". Simply logging out does not stop a container started with "-b"

systemd containers

systemd-nspawn and machinectl are lightweight container management tools.

They are deployed as part of systemd with the systemd-container package.

Usage example

Deploy FreedomBox on a Sid container. This will take around 1.2 GB of disk space.

# create a new container using debootstrap
$ CDIR=/var/lib/machines/freedombox
$ sudo debootstrap sid $CDIR
$ sudo systemd-nspawn -D $CDIR --machine FreedomBox
root@FreedomBox:~# apt-get install -y freedombox-setup

# set root password and stop the container
root@FreedomBox:~# passwd root
root@FreedomBox:~# ^D

# start the container and its services
$ sudo systemd-nspawn -D $CDIR --machine FreedomBox -b

# Browse to https://127.0.0.1/

# To stop the container, either issue:
$ sudo machinectl stop FreedomBox

# or log in and run "halt". Simply logging out does not stop a container started with "-b"