github issure
Because I removed a running container dir manually at /var/lib/docker/containers by mistake, then --privileged return error.
But it worked without --privileged.
$ docker run -d --name=hello --privileged=true hello-world
fd6cdf95eb1ed7617f4580eef556a2f64fff7b9afb144d346af3916d83704de4
docker: Error response from daemon: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: chown /sys/fs/cgroup/system.slice/docker-fd6cdf95eb1ed7617f4580eef556a2f64fff7b9afb144d346af3916d83704de4.scope/memory.oom.group: no such file or directory: unknown.
systemctl log:
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.182022716+08:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/3a42ea697432d31ffa04730b321526da2cb8e9490f9fc6edb68dda623e5bfa2c pid=645804
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.434396893+08:00" level=info msg="shim disconnected" id=3a42ea697432d31ffa04730b321526da2cb8e9490f9fc6edb68dda623e5bfa2c
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.434794719+08:00" level=warning msg="cleaning up after shim disconnected" id=3a42ea697432d31ffa04730b321526da2cb8e9490f9fc6edb68dda623e5bfa2c namespace=moby
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.434912272+08:00" level=info msg="cleaning up dead shim"
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.492815104+08:00" level=warning msg="cleanup warnings time=\"2022-01-27T14:30:28+08:00\" level=info msg=\"starting signal loop\" namespace=moby pid=645826\n"
1月 27 14:30:28 pi dockerd[630408]: time="2022-01-27T14:30:28.494742125+08:00" level=error msg="copy shim log" error="read /proc/self/fd/25: file already closed"
1月 27 14:30:28 pi dockerd[630400]: time="2022-01-27T14:30:28.501658261+08:00" level=error msg="stream copy error: reading from a closed fifo"
1月 27 14:30:28 pi dockerd[630400]: time="2022-01-27T14:30:28.501842720+08:00" level=error msg="stream copy error: reading from a closed fifo"
1月 27 14:30:28 pi dockerd[630400]: time="2022-01-27T14:30:28.931391572+08:00" level=error msg="3a42ea697432d31ffa04730b321526da2cb8e9490f9fc6edb68dda623e5bfa2c cleanup: failed to delete container from containerd: no such container"
docker version:
docker version [9:53:58]
Client:
Version: 20.10.12
API version: 1.41
Go version: go1.17.5
Git commit: e91ed5707e
Built: Tue Dec 14 20:49:29 2021
OS/Arch: linux/arm64
Context: default
Experimental: true
Server:
Engine:
Version: 20.10.12
API version: 1.41 (minimum version 1.12)
Go version: go1.17.5
Git commit: 459d0dfbbb
Built: Tue Dec 14 20:48:54 2021
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v1.5.9
GitCommit: 1407cab509ff0d96baa4f0eb6ff9980270e6e620.m
runc:
Version: 1.1.0
GitCommit: v1.1.0-0-g067aaf85
docker-init:
Version: 0.19.0
GitCommit: de40ad0
When I create a normal container, it works, but there is a caveat:Your kernel does not support memory limit capabilities or the cgroup is not mounted..
So I added cgroup_enable=memory cgroup_memory=1 at the end of the /boot/cmdline.txt and reboot.
And then all my problems were solved, although I still don't know why.
It is recommended to install docker from another host and copy the /usr/bin/runc file to the host with the problem
Related
I'm having a hard time figuring out what's wrong.
when I run docker-compose -f ./docker-compose.yml build parallel I get this output, saying that docker isn't running (which isn't true, see below)
joel#ogofe:/home/dev/udagram$ docker-compose -f ./docker-compose.yml build parallel
/home/joel/.local/lib/python3.9/site-packages/requests/__init__.py:109: RequestsDependencyWarning: urllib3 (1.26.9) or chardet (5.0.0)/charset_normalizer (2.0.6) doesn't match a supported version!
warnings.warn(
ERROR: Couldn't connect to Docker daemon at http://172.17.0.0:2375 - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
I've checked the status of the docker service, and it's up and running. I even tried restarting it to no avail.
Also worth knowing: I've scoured Stack Overflow for a fix, but haven't found one yet. I did get a nudge in the right direction (I hope) suggesting that it's a permission issue (ie docker-compose can't see the running service because it was started by the root user)
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-09-01 06:36:18 WAT; 2h 45min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 15087 (dockerd)
Tasks: 159
Memory: 34.2M
CPU: 5.999s
CGroup: /system.slice/docker.service
└─15087 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
Sep 01 06:35:46 ogofe dockerd[15087]: time="2022-09-01T06:35:46.555705337+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/cont>
Sep 01 06:35:46 ogofe dockerd[15087]: time="2022-09-01T06:35:46.555733870+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 01 06:35:49 ogofe dockerd[15087]: time="2022-09-01T06:35:49.830692206+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Sep 01 06:36:07 ogofe dockerd[15087]: time="2022-09-01T06:36:07.519863155+01:00" level=info msg="Loading containers: start."
Sep 01 06:36:15 ogofe dockerd[15087]: time="2022-09-01T06:36:15.201916110+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. >
Sep 01 06:36:15 ogofe dockerd[15087]: time="2022-09-01T06:36:15.796809326+01:00" level=info msg="Loading containers: done."
Sep 01 06:36:17 ogofe dockerd[15087]: time="2022-09-01T06:36:17.811988794+01:00" level=info msg="Docker daemon" commit=363e9a8 graphdriver(s)=overlay2 version=20.10.5
Sep 01 06:36:18 ogofe dockerd[15087]: time="2022-09-01T06:36:18.465597339+01:00" level=info msg="Daemon has completed initialization"
Sep 01 06:36:18 ogofe systemd[1]: Started Docker Application Container Engine.
Sep 01 06:36:18 ogofe dockerd[15087]: time="2022-09-01T06:36:18.893028725+01:00" level=info msg="API listen on /run/docker.sock"
However, running sudo docker-compose ... doesn't seem to work either, and I'm greeted with a new error. I am at a loss here, and I'm running out of time to submit this project.
joel#ogofe:/home/dev/udagram$ sudo docker-compose -f ./docker-compose.yml build parallel
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 5, in <module>
from compose.cli.main import main
ModuleNotFoundError: No module named 'compose'
I know my writing could use a lot of work, but I hope this is at least clear enough for someone to understand my challenge.
Thank You for the help. Cheers!
PS: I'm running on a Kali Linux distro, and I have docker-desktop installed.
I was able to get it working.
First I had to reinstall docker-compose by running curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/install/install_linux.sh | sh
I noticed that running sudo docker-compose was the wrong format of the command, instead I used sudo docker compose -f ./docker-compose-build.yml build --parallel and it worked fine.
Thanks #DavidMaze for your help.
Looking to fix this issue. I'm running RHEL7 with docker-compose 2.9.0. I've boiled things down to these files:
[<user>]$ ls -la
-rw-rw-r--. 1 glaisne glaisne 166 Aug 4 14:22 docker-compose.cloud-build.yml
-rw-rw-r--. 1 glaisne glaisne 76 Aug 4 14:04 .env.azure
drwxrwxr-x. 2 glaisne glaisne 24 Aug 4 14:12 helloWorld
[<user>]$ ls ./helloWorld
Dockerfile
[<user>]$ cat ./docker-compose.cloud-build.yml
version: '3.4'
services:
hello-world:
image: ${AZURE_DOCKER_REGISTRY}<servername>.hello-world:${DOCKER_IMAGE_TAG}
build:
context: ./helloWorld
[<user>]$ cat .env.azure
AZURE_DOCKER_REGISTRY=<server>.azurecr.io/
DOCKER_IMAGE_TAG=dev
[<user>]$ cat ./helloWorld/Dockerfile
FROM alpine
CMD ["echo", "Hello World"]
If I run
sudo docker-compose -f ./docker-compose.cloud-build.yml --env-file=./.env.azure build
I get this error:
[+] Building 0.0s (0/0)
listing workers for Build: failed to list workers: Unavailable: connection error: desc = "transport: Error while dialing unable to upgrade to h2c, received 404"
I am no Linux or docker guru, but I've done about all I can to fix this with no luck. The Docker service is running on the system (Docker version info below). Any insight on what this could be would be helpful. I've rebooted, Docker service has been given enough time to run, I don't see any network/firewall issues that I can tell ( from 404 ). I've even looked at the source (I don't speak go), and can't fine any reference to 'dial', 'h2c', 'workers.'
TIA
Docker version info:
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-209.git7d71120.el7_9.x86_64
Go version: go1.10.3
Git commit: 7d71120/1.13.1
Built: Fri Jan 7 13:15:46 2022
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-209.git7d71120.el7_9.x86_64
Go version: go1.10.3
Git commit: 7d71120/1.13.1
Built: Fri Jan 7 13:15:46 2022
OS/Arch: linux/amd64
Experimental: false
It seems that this problem has not yet been completely solved, but for the moment this may help you, try to set DOCKER_BUILDKIT=0 env var to disable the use of the buildkit API.
Reference: https://github.com/containers/podman/issues/13889
Note: If you use the sudo command for execute docker-compose please use the -E flag for preserve the env variables.
Scenario
I create a pool with multiple nodes (base image is Ubuntu Server 16.04), and provide the following start up command:
/bin/bash -c 'set -o pipefail; export DEBIAN_FRONTEND=noninteractive ; sudo -E apt update ; sudo -E apt upgrade -y ; sudo -E apt-get install -y --no-install-recommends apt-transport-https curl software-properties-common ; curl -fsSL "https://sks-keyservers.net/pks/lookup?op=get&search=0xee6d536cf7dc86e2d7d56f59a178ac6c6238f52e" | sudo -E apt-key add - ; sudo -E apt-add-repository "deb https://packages.docker.com/1.13/apt/repo/ ubuntu-$(lsb_release -cs) main" ; sudo -E apt-get update ; sudo -E apt-get install -y docker-engine ; sudo usermod -a -G docker $USER ; sudo -E service docker start ; journalctl -xe; wait'
The command servers the only purpose to install Docker Engine. Note also that I removed the option set -e in order to be able to run the command journalctl -xe and catch the following error.
Error
When creating the aforementioned pool, some nodes will fail the starting task. The behavior appears to be random, as not always a node fails, and, as mentioned, the other nodes do not fail.
The behavior does not depend on the size of the node (I tried both D2_v3 and NC6).
This is the output of journalctl -xe:
Oct 12 09:19:40 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has finished starting up.
--
-- The start-up result is done.
Oct 12 09:19:40 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 12 09:19:40 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:40.605332263Z" level=info msg="libcontainerd: new containerd process, pid: 24492"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.608293321Z" level=info msg="[graphdriver] using prior storage driver: aufs"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626089049Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626378756Z" level=warning msg="Your kernel does not support swap memory limit"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626558660Z" level=warning msg="Your kernel does not support cgroup rt period"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626698864Z" level=warning msg="Your kernel does not support cgroup rt runtime"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626834867Z" level=warning msg="Your kernel does not support cgroup blkio weight"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.626970070Z" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.627384080Z" level=info msg="Loading containers: start."
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.630900065Z" level=info msg="Firewalld running: false"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.661877309Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Oct 12 09:19:41 7d8bb094c57c400582f6031d59f1630000000A dockerd[24473]: time="2017-10-12T09:19:41.996853856Z" level=info msg="Loading containers: done."
Oct 12 09:19:42 7d8bb094c57c400582f6031d59f1630000000A kernel: aufs au_opts_verify:1585:dockerd[24490]: dirperm1 breaks the protection by the permission bits on the lower branch
Oct 12 09:19:45 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: docker.service: Main process exited, code=killed, status=11/SEGV
Oct 12 09:19:45 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Oct 12 09:19:45 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: docker.service: Unit entered failed state.
Oct 12 09:19:45 7d8bb094c57c400582f6031d59f1630000000A systemd[1]: docker.service: Failed with result 'signal'.
It appears that something went wrong in the creation of the network interface, but I'm not sure what and, especially, how to fix it.
Updated Answer, 2017-10-18:
The issue has been fixed with the latest platform image of Canonical UbuntuServer 16.04-LTS, and works with Go/Docker again.
Original Answer:
There's nothing wrong with your code. There's an issue with the Canonical UbuntuServer 16.04-LTS 201709190 platform image (which is, at this time, also latest) and Go/Docker.
Set the version of the image to deploy to 201708151 temporarily while the issue is fixed.
As an aside: if you're using Docker and Azure Batch, you should take a look at Batch Shipyard which provides this functionality. (full disclosure: I'm a contributor for this code.)
Installation with apt-get -y install docker-engine as described in https://docs.docker.com/engine/installation/linux/debian/ fails with
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
systemctl status docker.service gives
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Active: failed (Result: exit-code) since Sun 2017-02-19 11:03:55 CET; 1min 22s ago
Docs: https://docs.docker.com
Main PID: 5157 (code=exited, status=1/FAILURE)
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.594281147+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.595650295+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.640984406+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642147968+01:00" level=warning msg="Your kernel does not support oom control"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642181377+01:00" level=warning msg="Your kernel does not support memory swappiness"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642199036+01:00" level=warning msg="Your kernel does not support kernel memory limit"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642215415+01:00" level=warning msg="Unable to find cpu cgroup in mounts"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642262936+01:00" level=warning msg="Unable to find cpuset cgroup in mounts"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: time="2017-02-19T11:03:55.642312565+01:00" level=warning msg="mountpoint for pids not found"
Feb 19 11:03:55 v72089.1blu.de dockerd[5157]: Error starting daemon: Devices cgroup isn't mounted
The overlay module seems not to be installed on my distribution (it is a hosted virtual server).
uname -r
3.16.0-042stab120.11
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.7 (jessie)
Release: 8.7
Codename: jessie
Updating the kernel (https://backports.debian.org/Instructions/) with apt-get install -t jessie-backports linux-image-amd64 installs the overlay module in /lib/modules/4.9.0-0.bpo.1-amd64/kernel/fs/overlayfs/overlay.ko but this still doesn't allow me to install docker, I get the same error as mentioned above.
Edit: This is what docker version tells me
Client:
Version: 1.13.1
API version: 1.26
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 06:36:34 2017
OS/Arch: linux/amd64
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Edit 2: I have no problem with Docker on my Mac in VirtualBox Debian Jessie, that is why I think it is about the Debian distribution. One difference I found was that in the VB Debian there is storage driver "aufs" installed, in the hosted one, neither "aufs" nor "overlay".
Any ideas here? What can I do?
PS: I don't think the problem is related to that question error starting docker daemon on ubuntu 14.04 (Devices cgroup isn't mounted) as they don't have a storage driver problem.
Edit 3:
I tried this:
root#v72089:~# cat /etc/systemd/system/docker.service.d/00-execstart.conf
ExecStart=/usr/bin/dockerd -H fd:// --storage-driver aufs
root#v72089:~# systemctl daemon-reload && systemctl start docker
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
root#v72089:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─00-execstart.conf
Active: failed (Result: exit-code) since Mon 2017-02-20 09:38:53 CET; 9s ago
Docs: https://docs.docker.com
Process: 29655 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
Main PID: 29655 (code=exited, status=1/FAILURE)
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.185963477+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.187730948+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192048419+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192821521+01:00" level=warning msg="Your kernel does not support oom control"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192846291+01:00" level=warning msg="Your kernel does not support memory swappiness"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192862149+01:00" level=warning msg="Your kernel does not support kernel memory limit"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192872455+01:00" level=warning msg="Unable to find cpu cgroup in mounts"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192908839+01:00" level=warning msg="Unable to find cpuset cgroup in mounts"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: time="2017-02-20T09:38:53.192954496+01:00" level=warning msg="mountpoint for pids not found"
Feb 20 09:38:53 v72089.1blu.de dockerd[29655]: Error starting daemon: Devices cgroup isn't mounted
root#v72089:~# dockerd --storage-driver overlay
INFO[0000] libcontainerd: new containerd process, pid: 29703
ERRO[0001] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
Error starting daemon: error initializing graphdriver: driver not supported
root#v72089:~# find / -name overlay*
/lib/modules/4.9.0-0.bpo.1-amd64/kernel/fs/overlayfs
/lib/modules/4.9.0-0.bpo.1-amd64/kernel/fs/overlayfs/overlay.ko
root#v72089:~# dockerd --storage-driver aufs
INFO[0000] libcontainerd: new containerd process, pid: 29735
Error starting daemon: error initializing graphdriver: driver not supported
root#v72089:~# dockerd --storage-driver devicemapper
INFO[0000] libcontainerd: new containerd process, pid: 29785
Error starting daemon: error initializing graphdriver: driver not supported
To switch to another storage driver, you can add --storage-driver aufs to the dockerd startup command. With systemd, I believe you can simply run this as root:
mkdir -p /etc/systemd/system/docker.service.d
echo "ExecStart=/usr/bin/dockerd -H fd:// --storage-driver aufs" >/etc/systemd/system/docker.service.d/00-execstart.conf
Then systemctl daemon-reload && systemctl start docker. For the cgroups warnings, the linked answer for ubuntu should help. 3.16 is one of the first kernels docker supported, so not all of the features will be available with this kernel.
What finally solved my issue: talking with the host of the server. They seemed to use a different kernel that made it impossible to install Docker. I changed the server at the same host and everything worked fine.
I work with CentOS 7.0, and trying to configure docker, i used yum install docker for the docker installation.
when I start docker service, meets the follow problems:
[root#kiiby2r3 ~]# systemctl start docker.service
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
[root#kiiby2r3 ~]# systemctl status docker.service -l
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
Active: failed (Result: timeout) since Sun 2015-11-08 12:52:13 CST; 1h 3min ago
Docs: http://docs.docker.com
Main PID: 30368
Nov 08 12:48:35 kiiby2r3 docker[30368]: time="2015-11-08T12:48:35.968317600+08:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
Nov 08 12:48:36 kiiby2r3 docker[30368]: time="2015-11-08T12:48:36.028124500+08:00" level=error msg="WARNING: No --storage-opt dm.thinpooldev specified, using loopback; this configuration is strongly discouraged for production use"
Nov 08 12:49:34 kiiby2r3 systemd[1]: docker.service operation timed out. Terminating.
Nov 08 12:51:04 kiiby2r3 systemd[1]: docker.service stopping timed out (2). Killing.
Nov 08 12:52:13 kiiby2r3 systemd[1]: Failed to start Docker Application Container Engine.
Nov 08 12:52:14 kiiby2r3 systemd[1]: Unit docker.service entered failed state.
The CentOS release version:
[root#kiiby2r3 ~]# uname -a
Linux kiiby2r3 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[root#kiiby2r3 ~]# cat /etc/redhat-release
CentOS Linux release 7.0.1406 (Core)
Can somebody give me a hint?
Thank you!