OpenVZ Forum - RDF feed
type: channel
items: Docker into OpenVZ container
items: Re: Docker into OpenVZ container

Docker into OpenVZ container
type: item
description: Hello, i want to setup docker into openvz container with this howto: wiki.openvz.org/Docker_inside_CT . When i trying to run docker service, i have message about error in mounts: docker:~# bash -x /etc/init.d/docker start + set -e + export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin + PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin ++ basename /etc/init.d/docker + BASE=docker + DOCKER=/usr/bin/docker + DOCKER_PIDFILE=/var/run/docker.pid + DOCKER_SSD_PIDFILE=/var/run/docker-ssd.pid + DOCKER_LOGFILE=/var/log/docker.log + DOCKER_OPTS= + DOCKER_DESC=Docker + . /lib/lsb/init-functions +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)' ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']' ++ . /lib/lsb/init-functions.d/20-left-info-blocks ++ FANCYTTY= ++ '[' -e /etc/lsb-base-logging.sh ']' ++ true + '[' -f /etc/default/docker ']' + . /etc/default/docker + '[' -x /sbin/initctl ']' + '[' '!' -x /usr/bin/docker ']' + case "$1" in + fail_unless_root ++ id -u + '[' 0 '!=' 0 ']' + cgroupfs_mount + grep -v '^#' /etc/fstab + grep -q cgroup + '[' '!' -e /proc/cgroups ']' + '[' '!' -d /sys/fs/cgroup ']' + mountpoint -q /sys/fs/cgroup + cd /sys/fs/cgroup ++ awk '!/^#/ { if ($4 == 1) print $1 }' /proc/cgroups + for sys in '$(awk '\''!/^#/ { if ($4 == 1) print $1 }'\'' /proc/cgroups)' + mkdir -p cpuset + mountpoint -q cpuset + mount -n -t cgroup -o cpuset cgroup cpuset mount: wrong fs type, bad option, bad superblock on cgroup, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) In some cases useful info is found in syslog - try dmesg | tail or so + rmdir cpuset + for sys in '$(awk '\''!/^#/ { if ($4 == 1) print $1 }'\'' /proc/cgroups)' + mkdir -p cpu + mountpoint -q cpu + mount -n -t cgroup -o cpu cgroup cpu mount: wrong fs type, bad option, bad superb…
creator: wiuempe
date: 2015-05-21T08:35:59-00:00

Re: Docker into OpenVZ container
type: item
description: Hi wiuempe, I've been successful in getting Docker to run, but only on the following configuration: CentOS (6 or 7 with kernel 2.6.32-042stab108.2) host server with running a CentOS 7 container running Docker. The how-to on wiki.openvz.org/Docker_inside_CT works perfectly for my configuration. Except Docker uses up all inodes REALY fast so I'm still working on an optimal number for that.
creator: tburazin
date: 2015-06-19T19:41:06-00:00

Re: Docker into OpenVZ container
type: item
description: hello, i have the same issue but with centos 7 it did not work i have on start container this Error: CT-55555 /# docker start 12ed179e86a8 Error response from daemon: Cannot start container 12ed179e86a8: [8] System error: write /sys/fs/cgroup/cpuset/system.slice/docker-12ed179e86a8c5253e 8b02d1f21edd82cb443a48575471a3654f55578323282f.scope/cgroup. procs: no space left on device Error: failed to start containers: [12ed179e86a8] Handler for POST /containers/{name:.*}/start returned error: Cannot start container 12ed179e86a8: [8] System error: write /sys/fs/cgroup/cpuset/system.slice/docker-12ed179e86a8c5253e 8b02d1f21edd82cb443a48575471a3654f55578323282f.scope/cgroup. procs: no space left on device ERRO[1198] HTTP Error err=Cannot start container 12ed179e86a8: [8] System error: write /sys/fs/cgroup/cpuset/system.slice/docker-12ed179e86a8c5253e 8b02d1f21edd82cb443a48575471a3654f55578323282f.scope/cgroup. procs: no space left on device statusCode=500 I thin docker an Virtuozzo does work together. This is not was Marketing said.
creator: locara
date: 2016-03-15T22:55:22-00:00

Re: Docker into OpenVZ container
type: item
description: So how many inodes did you assign to your VM?
creator: Ales
date: 2016-03-23T13:19:50-00:00

Re: Docker into OpenVZ container
type: item
description: Hallo, Thank for answer, i use one namenöde an two Datenode. But the issue is exactly i iwant to run the Container.
creator: locara
date: 2016-03-23T13:28:15-00:00

Re: Docker into OpenVZ container
type: item
description: I think you misunderstood me. The "inode" is a very specific filesystem term. The amount of inodes is something you set for each container. I haven't used docker and openvz together, but I see tburazin mentioning large demand for inodes due to docker. The lack of inodes could quite possibly translate into device space errors so I would advise you to check how much inodes have you assigned to a container running docker and try assigning more.
creator: Ales
date: 2016-03-26T21:25:44-00:00

Re: Docker into OpenVZ container
type: item
description: Thanks verry much, Where can i change this terms, in openVZ container?
creator: locara
date: 2016-03-27T06:47:49-00:00

Re: Docker into OpenVZ container
type: item
description: Hi locara, the number of inodes is set per container. If you are experiencing a shortage of inodes you can check with the command: vzctl exec CTID df -i You can find some explanation regarding disk quotas here: https://openvz.org/Resource_shortage#Disk_quota The command to change number of inodes is: vzctl set CTID --diskinodes softlimit:hardlimit --save eg: vzctl set 101 --diskinodes 5000000:5500000 --save The default size is 2000000:2200000 if I remember correctly and it's recommended to allocate 200000 inodes per GB hard drive (for softlimit) and 220000 inodes per GB hard drive (hardlimit) You can go with a different amount, but be careful not to use up all your inodes on one container.
creator: tburazin
date: 2016-03-27T09:31:56-00:00