Difference between pages "Linux Containers/pt-br" and "Translations:Metro/122/en"

< Linux Containers(Difference between pages)
(Install LXC kernel)
 
(Importing a new version from external source)
 
Line 1: Line 1:
== Status ==
+
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:
 
+
Como no kernel Linux 3.1.5, o LXC é útil por isolar seus próprios trabalhos de outros. Ele não está pronto ainda para isolar potencialmente usuários de outros ou do sistema hospede (host). Para uma solução solução de containers mais madura que é apropriada para ambientes de hospedagem, veja [[OpenVZ]].
+
 
+
Containers LXC ainda não possui seu próprio sistema de atualização, e eles veem tudo que está na saída {{c|dmesg}} no host, enter outras coisas. Mas em geral, a tecnologia funciona.
+
 
+
== Informações Básicas ==
+
 
+
 
+
* Linux Containers são baseados em:
+
** Kernel namespaces para isolamento de recurso
+
** CGroups para limitação e contabilidade de recurso
+
 
+
{{Package|app-emulation/lxc}} é a ferramenta userspace para os Linux containers
+
 
+
== Grupos de controle (Control groups) ==
+
 
+
* Control groups (cgroups) no kernel desde o 2.6.24
+
** Permite agregação de tarefas e seus filhos (children)
+
** Subsystems (cpuset, memory, blkio,...)
+
** accounting - para medir quanto de recursos certos sistemas utilizam
+
** resource limiting (limitante de recurso) - grupos podem ser definidos para não exceder uma definição de limite de memória
+
** prioritization (priorização) - alguns grupos pode obter um compartilhamento maior de CPU
+
** control - freezing/unfreezing (congelamento/descongelamento) de cgroups, checkpointing (ponto de verificação) e restarting (reinicialização)
+
** No disk quota limitation ( -> image file, LVM, XFS, directory tree quota,...) [sem limitação de cota de disco (-> arquivo imagem, LVM, XFS, cota de arvore de diretório)]
+
 
+
== Subsystems ==
+
<br>
+
{{console|body=
+
###i## cat /proc/cgroups
+
subsys_name hierarchy num_cgroups enabled
+
cpuset
+
cpu
+
cpuacct
+
memory
+
devices
+
freezer
+
blkio
+
perf_event
+
hugetlb
+
}}
+
 
+
#cpuset    -> limita tarefas para CPU/CPUs específicos
+
#cpu        -> compartilhamento de CPU
+
#cpuacct    -> contabilização de CPU
+
#memory    -> limitação de contabilização de memória e de swap
+
#devices    -> lista de dispositivo negado ou permitido
+
#freezer    -> suspend/resume tarefas
+
#blkio      -> priorização I/O (weight, throttle, ...)
+
#perf_event -> suporte para monitoramento por-cpu por-cgroup [http://lwn.net/Articles/421574/ perf_events]
+
#hugetlb    -> recurso controlador do cgroup para páginas HugeTLB [http://lwn.net/Articles/499255/ hugetlb]
+
 
+
== Configuring the Funtoo Host System ==
+
 
+
=== Instale o LXC kernel ===
+
Qualquer kernel que vão além do 3.1.5 provavelmente funcionarão. Pessoalmente eu prefiro {{Package|sys-kernel/gentoo-sources}} já que esses possuem suporte para todos os namespaces sem sacrificar o suporte ao xfs, FUSE ou NFS por exemplo. Essas verificações foram introduzidas depois iniciando a partir do 3.5, Isso pode também significar que o user namespace não está funcionando opcionalmente.
+
 
+
* User namespace (EXPERIMENTAL) depende do EXPERIMENTAL e do UIDGID_CONVERTED
+
** config UIDGID_CONVERTED
+
*** True (verdadeiro) se todos os componentes de software selecionados forem conhecidos por terem uid_t and gid_t convertidos para kuid_t and kgid_t onde se apropriaram e são por outro lado seguros de utilizar com o user namespace.
+
**** Networking - depende do NET_9P = n
+
**** Filesystems - 9P_FS = n, AFS_FS = n, AUTOFS4_FS = n, CEPH_FS = n, CIFS = n, CODA_FS = n, FUSE_FS = n, GFS2_FS = n, NCP_FS = n, NFSD = n, NFS_FS = n, OCFS2_FS = n, XFS_FS = n
+
**** Opções de segurança (Security options) - Grsecurity - GRKERNSEC = n (se aplicável)
+
 
+
** As of 3.10.xx kernel, all of the above options are safe to use with User namespaces, except for XFS_FS, therefore with kernel >=3.10.xx, you should answer XFS_FS = n, if you want User namespaces support.
+
** in your kernel source directory, you should check init/Kconfig and find out what UIDGID_CONVERTED depends on
+
 
+
==== Kernel configuration ====
+
These options should be enable in your kernel to be able to take full advantage of LXC.
+
 
+
* General setup
+
** CONFIG_NAMESPACES
+
*** CONFIG_UTS_NS
+
*** CONFIG_IPC_NS
+
*** CONFIG_PID_NS
+
*** CONFIG_NET_NS
+
*** CONFIG_USER_NS
+
** CONFIG_CGROUPS
+
*** CONFIG_CGROUP_DEVICE
+
*** CONFIG_CGROUP_SCHED
+
*** CONFIG_CGROUP_CPUACCT
+
*** CONFIG_CGROUP_MEM_RES_CTLR (in 3.6+ kernels it's called CONFIG_MEMCG)
+
*** CONFIG_CGROUP_MEM_RES_CTLR_SWAP (in 3.6+ kernels it's called CONFIG_MEMCG_SWAP)
+
*** CONFIG_CPUSETS (on multiprocessor hosts)
+
* Networking support
+
** Networking options
+
*** CONFIG_VLAN_8021Q
+
* Device Drivers
+
** Character devices
+
*** Unix98 PTY support
+
**** CONFIG_DEVPTS_MULTIPLE_INSTANCES
+
** Network device support
+
*** Network core driver support
+
**** CONFIG_VETH
+
**** CONFIG_MACVLAN
+
 
+
Once you have lxc installed, you can then check your kernel config with:
+
{{console|body=
+
# ##i##CONFIG=/path/to/config /usr/sbin/lxc-checkconfig
+
}}
+
 
+
=== Emerge lxc ===
+
{{console|body=
+
# ##i##emerge app-emulation/lxc
+
}}
+
 
+
=== Configure Networking For Container ===
+
 
+
Typically, one uses a bridge to allow containers to connect to the network. This is how to do it under Funtoo Linux:
+
 
+
# create a bridge using the Funtoo network configuration scripts. Name the bridge something like {{c|brwan}} (using {{c|/etc/init.d/netif.brwan}}). Configure your bridge to have an IP address.
+
# Make your physical interface, such as {{c|eth0}}, an interface with no IP address (use the Funtoo {{c|interface-noip}} template.)
+
# Make {{c|netif.eth0}} a slave of {{c|netif.brwan}} in {{c|/etc/conf.d/netif.brwan}}.
+
# Enable your new bridged network and make sure it is functioning properly on the host.
+
 
+
You will now be able to configure LXC to automatically add your container's virtual ethernet interface to the bridge when it starts, which will connect it to your network.
+
== Setting up a Funtoo Linux LXC Container ==
+
 
+
Here are the steps required to get Funtoo Linux running <i>inside</i> a container. The steps below show you how to set up a container using an existing Funtoo Linux OpenVZ template. It is now also possible to use [[Metro]] to build an lxc container tarball directly, which will save you manual configuration steps and will provide an {{c|/etc/fstab.lxc}} file that you can use for your host container config. See [[Metro Recipes]] for info on how to use Metro to generate an lxc container.
+
 
+
=== Create and Configure Container Filesystem ===
+
 
+
# Start with a Funtoo LXC template, and unpack it to a directory such as {{c|/lxc/funtoo0/rootfs/}}
+
# Create an empty {{c|/lxc/funtoo0/fstab}} file
+
# Ensure {{c|c1}} line is uncommented (enabled) and {{c|c2}} through {{c|c6}} lines are disabled in {{c|/lxc/funtoo0/rootfs/etc/inittab}}
+
 
+
That's almost all you need to get the container filesystem ready to start.
+
 
+
=== Create Container Configuration Files ===
+
 
+
Create the following files:
+
 
+
==== {{c|/lxc/funtoo0/config}} ====
+
 
+
 
+
and also create symlink from
+
==== {{c|/lxc/funtoo0/config to /etc/lxc/funtoo0/config }} ====
+
{{console|body=
+
###i## install -d /etc/lxc/funtoo0
+
###i## ln -s /lxc/funtoo0/config /etc/lxc/funtoo0/config
+
}}
+
 
+
{{note| Daniel Robbins needs to update this config to be more in line with http://wiki.progress-linux.org/software/lxc/ -- this config appears to have nice, refined device node permissions and other goodies. // note by Havis to Daniel, this config is already superior.}}
+
 
+
 
+
Read "man 5 lxc.conf" , to get more information about linux container configuration file.
+
<pre>
+
## Container
+
lxc.utsname                            = funtoo0
+
lxc.rootfs                              = /lxc/funtoo0/rootfs/
+
lxc.arch                                = x86_64
+
#lxc.console                            = /var/log/lxc/funtoo0.console  # uncomment if you want to log containers console
+
lxc.tty                                = 6  # if you plan to use container with physical terminals (eg F1..F6)
+
#lxc.tty                                = 0  # set to 0 if you dont plan to use the container with physical terminal, also comment out in your containers /etc/inittab  c1 to c6 respawns (e.g. c1:12345:respawn:/sbin/agetty 38400 tty1 linux)
+
lxc.pts                                = 1024
+
 
+
 
+
## Capabilities
+
lxc.cap.drop                            = audit_control
+
lxc.cap.drop                            = audit_write
+
lxc.cap.drop                            = mac_admin
+
lxc.cap.drop                            = mac_override
+
lxc.cap.drop                            = mknod
+
lxc.cap.drop                            = setfcap
+
lxc.cap.drop                            = setpcap
+
lxc.cap.drop                            = sys_admin
+
#lxc.cap.drop                            = sys_boot # capability to reboot the container
+
#lxc.cap.drop                            = sys_chroot # required by SSH
+
lxc.cap.drop                            = sys_module
+
#lxc.cap.drop                            = sys_nice
+
lxc.cap.drop                            = sys_pacct
+
lxc.cap.drop                            = sys_rawio
+
lxc.cap.drop                            = sys_resource
+
lxc.cap.drop                            = sys_time
+
#lxc.cap.drop                            = sys_tty_config # required by getty
+
 
+
## Devices
+
#lxc.cgroup.devices.allow              = a # Allow access to all devices
+
lxc.cgroup.devices.deny                = a # Deny access to all devices
+
 
+
# Allow to mknod all devices (but not using them)
+
lxc.cgroup.devices.allow                = c *:* m
+
lxc.cgroup.devices.allow                = b *:* m
+
 
+
lxc.cgroup.devices.allow                = c 1:3 rwm # /dev/null
+
lxc.cgroup.devices.allow                = c 1:5 rwm # /dev/zero
+
lxc.cgroup.devices.allow                = c 1:7 rwm # /dev/full
+
lxc.cgroup.devices.allow                = c 1:8 rwm # /dev/random
+
lxc.cgroup.devices.allow                = c 1:9 rwm # /dev/urandom
+
#lxc.cgroup.devices.allow                = c 4:0 rwm # /dev/tty0 ttys not required if you have lxc.tty = 0
+
#lxc.cgroup.devices.allow                = c 4:1 rwm # /dev/tty1 devices with major number 4 are "real" tty devices
+
#lxc.cgroup.devices.allow                = c 4:2 rwm # /dev/tty2
+
#lxc.cgroup.devices.allow                = c 4:3 rwm # /dev/tty3
+
lxc.cgroup.devices.allow                = c 5:0 rwm # /dev/tty
+
lxc.cgroup.devices.allow                = c 5:1 rwm # /dev/console
+
lxc.cgroup.devices.allow                = c 5:2 rwm # /dev/ptmx
+
lxc.cgroup.devices.allow                = c 10:229 rwm # /dev/fuse
+
lxc.cgroup.devices.allow                = c 136:* rwm # /dev/pts/* devices with major number 136 are pts
+
lxc.cgroup.devices.allow                = c 254:0 rwm # /dev/rtc0
+
 
+
## Limits#
+
lxc.cgroup.cpu.shares                  = 1024
+
lxc.cgroup.cpuset.cpus                = 0        # limits container to CPU0
+
lxc.cgroup.memory.limit_in_bytes      = 512M
+
lxc.cgroup.memory.memsw.limit_in_bytes = 1G
+
#lxc.cgroup.blkio.weight                = 500      # requires cfq block scheduler
+
 
+
## Filesystem
+
#containers fstab should be outside it's rootfs dir (e.g. /lxc/funtoo0/fstab is ok, but /lxc/funtoo0/rootfs/etc/fstab is wrong!!!)
+
#lxc.mount                              = /lxc/funtoo0/fstab     
+
 
+
#lxc.mount.entry is prefered, because it supports relative paths
+
lxc.mount.entry                        = proc proc proc nosuid,nodev,noexec  0 0
+
lxc.mount.entry                        = sysfs sys sysfs nosuid,nodev,noexec,ro 0 0
+
lxc.mount.entry                        = devpts dev/pts devpts nosuid,noexec,mode=0620,ptmxmode=000,newinstance 0 0
+
lxc.mount.entry                        = tmpfs dev/shm tmpfs nosuid,nodev,mode=1777 0 0
+
lxc.mount.entry                        = tmpfs run tmpfs nosuid,nodev,noexec,mode=0755,size=128m 0 0
+
lxc.mount.entry                        = tmpfs tmp tmpfs nosuid,nodev,noexec,mode=1777,size=1g 0 0
+
 
+
##Example of having /var/tmp/portage as tmpfs in container
+
#lxc.mount.entry                        = tmpfs var/tmp/portage tmpfs defaults,size=8g,uid=250,gid=250,mode=0775 0 0
+
##Example of bind mount
+
#lxc.mount.entry                        = /srv/funtoo0 /lxc/funtoo0/rootfs/srv/funtoo0 none defaults,bind 0 0
+
 
+
## Network
+
lxc.network.type                        = veth
+
lxc.network.flags                      = up
+
lxc.network.hwaddr                      = #put your MAC address here, otherwise you will get a random one
+
lxc.network.link                        = br0
+
lxc.network.name                        = eth0
+
#lxc.network.veth.pair                  = veth-example
+
</pre>
+
 
+
Read "man 7 capabilities" to get more information aboout Linux capabilities.
+
 
+
Above, use the following command to generate a random MAC for {{c|lxc.network.hwaddr}}:
+
 
+
{{console|body=
+
###i## openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//'
+
}}
+
 
+
It is a very good idea to assign a static MAC address to your container using {{c|lxc.network.hwaddr}}. If you don't, LXC will auto-generate a new random MAC every time your container starts, which may confuse network equipment that expects MAC addresses to remain constant.
+
 
+
It might happen from case to case that you aren't able to start your LXC Container with the above generated MAC address so for all these who run into that problem here is a little script that connects your IP for the container with the MAC address. Just save the following code as {{c|/etc/lxc/hwaddr.sh}}, make it executable and run it like {{c|/etc/lxc/hwaddr.sh xxx.xxx.xxx.xxx}} where xxx.xxx.xxx.xxx represents your Container IP. <br>{{c|/etc/lxc/hwaddr.sh}}:
+
 
+
<pre>
+
#!/bin/sh
+
IP=$*
+
HA=`printf "02:00:%x:%x:%x:%x" ${IP//./ }`
+
echo $HA
+
</pre>
+
 
+
==== {{c|/lxc/funtoo0/fstab}} ====
+
{{fancynote| It is now preferable to have mount entries directly in config file instead of separate fstab:}}
+
Edit the file {{c|/lxc/funtoo0/fstab}}:
+
<pre>
+
none /lxc/funtoo0/dev/pts devpts defaults 0 0
+
none /lxc/funtoo0/proc proc defaults 0 0
+
none /lxc/funtoo0/sys sysfs defaults 0 0
+
none /lxc/funtoo0/dev/shm tmpfs nodev,nosuid,noexec,mode=1777,rw 0 0
+
</pre>
+
== LXC Networking ==
+
*veth - Virtual Ethernet (bridge)
+
*vlan - vlan interface (requires device able to do vlan tagging)
+
*macvlan (mac-address based virtual lan tagging) has 3 modes:
+
**private
+
**vepa (Virtual Ethernet Port Aggregator)
+
**bridge
+
*phys - dedicated host NIC
+
[https://blog.flameeyes.eu/2010/09/linux-containers-and-networking Linux Containers and Networking]
+
 
+
Enable routing on the host:
+
By default Linux workstations and servers have IPv4 forwarding disabled.
+
{{console|body=
+
###i## echo "1" > /proc/sys/net/ipv4/ip_forward
+
###i## cat /proc/sys/net/ipv4/ip_forward
+
# 1
+
}}
+
== Initializing and Starting the Container ==
+
 
+
You will probably need to set the root password for the container before you can log in. You can use chroot to do this quickly:
+
 
+
{{console|body=
+
###i## chroot /lxc/funtoo0/rootfs
+
(chroot) ###i## passwd
+
New password: XXXXXXXX
+
Retype new password: XXXXXXXX
+
passwd: password updated successfully
+
(chroot) ###i## exit
+
}}
+
 
+
Now that the root password is set, run:
+
 
+
{{console|body=
+
###i## lxc-start -n funtoo0 -d
+
}}
+
 
+
The {{c|-d}} option will cause it to run in the background.
+
 
+
To attach to the console:
+
 
+
{{console|body=
+
###i## lxc-console -n funtoo0
+
}}
+
 
+
You should now be able to log in and use the container. In addition, the container should now be accessible on the network.
+
 
+
To directly attach to container:
+
 
+
{{console|body=
+
###i## lxc-attach -n funtoo0
+
}}
+
 
+
To stop the container:
+
 
+
{{console|body=
+
###i## lxc-stop -n funtoo0
+
}}
+
 
+
Ensure that networking is working from within the container while it is running, and you're good to go!
+
== Starting LXC container during host boot ==
+
 
+
# You need to create symlink in {{c|/etc/init.d/}} to {{c|/etc/init.d/lxc}} so that it reflects your container.
+
# {{c|ln -s /etc/init.d/lxc /etc/init.d/lxc.funtoo0}}
+
# now you can add {{c|lxc.funtoo0}} to default runlevel
+
# {{c|rc-update add lxc.funtoo0 default}}
+
{{console|body=
+
###i## rc
+
* Starting funtoo0 ...                  [ ok ]
+
}}
+
== LXC Bugs/Missing Features ==
+
 
+
This section is devoted to documenting issues with the current implementation of LXC and its associated tools. We will be gradually expanding this section with detailed descriptions of problems, their status, and proposed solutions.
+
 
+
=== reboot ===
+
 
+
* By default, lxc does not support rebooting a container from within. It will simply stop and the host will not know to start it.
+
* If you want your container to reboot gracefully, you need sys_boot capability (comment out lxc.cap.drop = sys_boot in your container config)
+
 
+
=== PID namespaces ===
+
 
+
Process ID namespaces are functional, but the container can still see the CPU utilization of the host via the system load (ie. in {{c|top}}).
+
 
+
=== /dev/pts newinstance ===
+
 
+
* Some changes may be required to the host to properly implement "newinstance" {{c|/dev/pts}}. See [https://bugzilla.redhat.com/show_bug.cgi?id=501718 This Red Hat bug].
+
 
+
=== lxc-create and lxc-destroy ===
+
 
+
* LXC's shell scripts are badly designed and are sure way to destruction, avoid using lxc-create and lxc-destroy.
+
 
+
=== network initialization and cleanup ===
+
 
+
* If used network.type = phys after lxc-stop the interface will be renamed to value from lxc.network.link. It supposed to be fixed in 0.7.4, happens still on 0.7.5 - http://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg01760.html
+
 
+
* Re-starting a container can result in a failure as network resource are tied up from the already-defunct instance: [http://www.mail-archive.com/lxc-devel@lists.sourceforge.net/msg00824.html]
+
 
+
=== graceful shutdown ===
+
 
+
* To gracefully shutdown a container, it's init system needs to properly handle kill -PWR signal
+
* For funtoo/gentoo make sure that you have:
+
** pf:12345:powerwait:/sbin/halt
+
** in your containers /etc/inittab
+
* For debian/ubuntu make sure that you have:
+
** pf::powerwait:/sbin/shutdown -t1 -a -h now
+
** in your container /etc/inittab
+
** and also comment out other line starting with pf:powerfail (such as pf::powerwait:/etc/init.d/powerfail start) <- these are used if you have UPS monitoring daemon installed!
+
* /etc/init.d/lxc seems to have broken support for graceful shutdown (it sends proper signal, but then also tries to kill the init with lxc-stop)
+
 
+
=== funtoo ===
+
 
+
* Our udev should be updated to contain {{c|-lxc}} in scripts. (This has been done as of 02-Nov-2011, so should be resolved. But not fixed in our openvz templates, so need to regen them in a few days.)
+
* Our openrc should be patched to handle the case where it cannot mount tmpfs, and gracefully handle this situation somehow. (Work-around in our docs above, which is to mount tmpfs to {{c|/libexec/rc/init.d}} using the container-specific {{c|fstab}} file (on the host.)
+
* Emerging udev within a container can/will fail when realdev is run, if a device node cannot be created (such as /dev/console) if there are no mknod capabilities within the container. This should be fixed.
+
== References ==
+
 
+
* {{c|man 7 capabilities}}
+
* {{c|man 5 lxc.conf}}
+
== Links ==
+
 
+
* There are a number of additional lxc features that can be enabled via patches: [http://lxc.sourceforge.net/patches/linux/3.0.0/3.0.0-lxc1/]
+
* [https://wiki.ubuntu.com/UserNamespace Ubuntu User Namespaces page]
+
* lxc-gentoo setup script [https://github.com/globalcitizen/lxc-gentoo on GitHub]
+
 
+
* '''IBM developerWorks'''
+
** [http://www.ibm.com/developerworks/linux/library/l-lxc-containers/index.html LXC: Linux Container Tools]
+
** [http://www.ibm.com/developerworks/linux/library/l-lxc-security/ Secure Linux Containers Cookbook]
+
 
+
* '''Linux Weekly News'''
+
** [http://lwn.net/Articles/244531/ Smack for simplified access control]
+
 
+
[[Category:Labs]]
+
[[Category:HOWTO]]
+
[[Category:Virtualization]]
+

Latest revision as of 17:31, July 12, 2015

On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: