LXC: Difference between revisions
No edit summary |
|||
Line 75: | Line 75: | ||
This will erase eerything, without asking any questions. It is equivalent to: {{Cmd|rm -r /var/lib/lxc/guest1}} | This will erase eerything, without asking any questions. It is equivalent to: {{Cmd|rm -r /var/lib/lxc/guest1}} | ||
== VirtualBox == | |||
== Advanced == | |||
{{Cmd|lxc-checkconfig}} | |||
{{Cmd| | |||
Kernel configuration not found at /proc/config.gz; searching... | |||
Kernel configuration found at /boot/config-3.10.13-1-grsec | |||
--- Namespaces --- | |||
Namespaces: enabled | |||
Utsname namespace: enabled | |||
Ipc namespace: enabled | |||
Pid namespace: enabled | |||
User namespace: missing | |||
Network namespace: enabled | |||
Multiple /dev/pts instances: enabled | |||
--- Control groups --- | |||
Cgroup: enabled | |||
Cgroup clone_children flag: enabled | |||
Cgroup device: enabled | |||
Cgroup sched: enabled | |||
Cgroup cpu account: enabled | |||
Cgroup memory controller: missing | |||
Cgroup cpuset: enabled | |||
--- Misc --- | |||
Veth pair device: enabled | |||
Macvlan: enabled | |||
Vlan: enabled | |||
File capabilities: enabled | |||
Note : Before booting a new kernel, you can check its configuration | |||
usage : CONFIG{{=}}/path/to/config /usr/bin/lxc-checkconfig | |||
}} | |||
=== VirtualBox === | |||
In order for network to work on containers you need to set "Promiscuous Mode" to "Allow All" in VirtualBox settings for the network adapter. | In order for network to work on containers you need to set "Promiscuous Mode" to "Allow All" in VirtualBox settings for the network adapter. |
Revision as of 08:23, 3 October 2013
Linux Containers (LXC) provides containers similar BSD Jails, Linux VServer and Solaris Zones. It gives the impression of virtualization, but shares the kernel and resources with the "host".
Installation
Install the required packages:
apk add lxc bridge
Prepare network on host
Set up a bridge on the host. Example /etc/network/interfaces:
auto br0 iface br0 inet dhcp bridge-ports eth0
Create a network configuration template for the guests, /etc/lxc/lxc.conf:
lxc.network.type = veth lxc.network.link = br0 lxc.network.flags = up
Create a guest
Alpine Template
lxc-create -n guest1 -f /etc/lxc/lxc.conf -t alpine
This will create a /var/lib/lxc/guest1 directory with a config file and a rootfs directory.
Note that by default alpine template does not have networking service on, you will need to add it using lxc-console
Debian template
In order to create a debian template container you will need to install some packages:
apk add debootstrap rsync
Also you will need to turn off some grsecurity chroot options otherwise the debootstrap will fail:
echo 0 > /proc/sys/kernel/grsecurity/chroot_caps echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_chroot echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mount echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mknod echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_chmod
Please remember to turn them back on, or just simply reboot the system.
Now you can run:
SUITE=wheezy lxc-create -n guest1 -f /etc/lxc/lxc.conf -t debian
Starting/Stopping the guest
Create a symlink to the /etc/init.d/lxc script for your guest.
ln -s lxc /etc/init.d/lxc.guest1
You can start your guest with:
/etc/init.d/lxc.guest1 start
Stop it with:
/etc/init.d/lxc.guest1 stop
Make it autostart on boot up with:
rc-update add lxc.guest1
Connecting to the guest
By default sshd is not installed, so you will have to connect to a virtual console. This is done with:
lxc-console -n guest1
To disconnect from it, press Ctrl+a q
Deleting a guest
Make sure the guest is stopped and run:
lxc-destroy -n guest1
This will erase eerything, without asking any questions. It is equivalent to:
rm -r /var/lib/lxc/guest1
Advanced
lxc-checkconfig
Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.10.13-1-grsec --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: missing Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup clone_children flag: enabled Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: missing Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
VirtualBox
In order for network to work on containers you need to set "Promiscuous Mode" to "Allow All" in VirtualBox settings for the network adapter.