mirror of
https://github.com/Ponce/slackbuilds
synced 2024-11-28 10:02:43 +01:00
f20658c5b7
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org> |
||
---|---|---|
.. | ||
config | ||
docker-btrfs.patch | ||
docker.info | ||
docker.SlackBuild | ||
doinst.sh | ||
README | ||
slack-desc |
Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. To use docker as a limited user, add your user to the 'docker' group: # groupadd -r -g 281 docker # usermod -a -G docker <your_username> This will require logging out and back in. To have the docker daemon start and stop with your host, add to /etc/rc.d/rc.local: if [ -x /etc/rc.d/rc.docker ]; then /etc/rc.d/rc.docker start fi and to /etc/rc.d/rc.local_shutdown (creating it if needed): if [ -x /etc/rc.d/rc.docker ]; then /etc/rc.d/rc.docker stop fi For cgroups, docker does not support mounting cgroups on the "all" single hierarchy controller, but rather the individual controllers. To accomplish this, add the following to your /etc/fstab: cgroup /cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cgroup /cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /cgroup/freezer cgroup rw,relatime,freezer 0 0 cgroup /cgroup/net_cls cgroup rw,relatime,net_cls 0 0 cgroup /cgroup/blkio cgroup rw,relatime,blkio 0 0 And in addition, add to /etc/cgconfig.conf the following: mount { cpuset = /cgroup/cpuset; cpu = /cgroup/cpu; cpuacct = /cgroup/cpuacct; memory = /cgroup/memory; devices = /cgroup/devices; freezer = /cgroup/freezer; net_cls = /cgroup/net_cls; blkio = /cgroup/blkio; } If you are interested in enabling cgroup memory resource controll over swap as well, then append "swapaccount=1" to your kernel's parameters. This is often in /etc/lilo.conf, on the "append" variable. NOTE: google-go-lang is only needed at compile time - not needed for runtime.