systemd (for some time now) provides a powerful chroot alternative to linux users for creating quick and lightweight system containers using power of cgroups and socket activation.
There is a lot more to "systemd" than this, but that's for some other post. Until then can explore it, starting here.
There is a utility "systemd-nspawn" provided by systemd which acts as container manager. This is what can be used to easily spawn a new linux container and manage it. It has been updated with (the systemd's amazing trademark feature) Socket Activation.
This enables any container to make parent/host's systemd instance to listen at different service ports for itself. Only when those service ports receive a connection, these container will spawn and act to it. Voila, resource utilization and scalability concepts.
More of this can read in detail at: http://0pointer.de/blog/projects/socket-activated-containers.html
Here we'll see some way to quickly start using it via some custom made commands.
All the script commands used here can referred from https://github.com/abhishekkr/tux-svc-mux/blob/master/shell_profile/a.virt.sh as well.
Just download and source the linked script in your shell, and the commands told here will be available...
And yes, your system also need to be running systemd already.
Currently this just lets you create archlinux containers, will soon create different containers and make the script mature.
In case you don't have any created container already, or wanna create a new one...
---
---
There is a lot more to "systemd" than this, but that's for some other post. Until then can explore it, starting here.
There is a utility "systemd-nspawn" provided by systemd which acts as container manager. This is what can be used to easily spawn a new linux container and manage it. It has been updated with (the systemd's amazing trademark feature) Socket Activation.
This enables any container to make parent/host's systemd instance to listen at different service ports for itself. Only when those service ports receive a connection, these container will spawn and act to it. Voila, resource utilization and scalability concepts.
More of this can read in detail at: http://0pointer.de/blog/projects/socket-activated-containers.html
Here we'll see some way to quickly start using it via some custom made commands.
All the script commands used here can referred from https://github.com/abhishekkr/tux-svc-mux/blob/master/shell_profile/a.virt.sh as well.
Just download and source the linked script in your shell, and the commands told here will be available...
And yes, your system also need to be running systemd already.
Currently this just lets you create archlinux containers, will soon create different containers and make the script mature.
In case you don't have any created container already, or wanna create a new one...
$ nspawn-archTo list names of all created containers...
$ nspawn-ls
To stop a running container...
$ nspawn-stop
To start an already created conatiner
$ nspawn-start
---
