verified docker.service file, path is proper /usr/bin/dockerd. ubuntu@vm1-sdnc:/opt$ cat /usr/bin/docker docker docker-containerd-ctr dockerd docker-proxy docker-containerd docker-containerd-shim docker-init docker-runc
[Service] Type=notify # the default is not to use systemd for cgroups because the delegate issues still # exists and systemd currently does not support the cgroup feature set required # for containers run by docker ExecStart=/usr/bin/dockerd -H fd:// --mtu=1450 ExecReload=/bin/kill -s HUP $MAINPID LimitNOFILE=1048576 # Having non-zero Limit*s causes performance problems due to accounting overhead From: Elhay Efrat [mailto:elhay.efr...@amdocs.com] Sent: 2017年10月25日 16:24 To: Shashikanth vh; onap-discuss@lists.onap.org; onap-s...@lists.onap.org Subject: RE: [onap-discuss] [sdnc]could not able to see dockers running Please try vi /etc/systemd/system/docker.service Had a -d in the place of the daemon at Execstart. That wasn't the case for me. I had ...daemon -D..., but I did notice that it was pointing to /usr/bin/local/docker. That didn't exist, but what does exist is /usr/bin/docker. In that location you will also find docker-containerd, dockerd, etc... Anyway, I made the change to the docker.service file--simply dropping /local out of there. Saved. Then: $ systemctl daemon-reload $ sudo service docker restart $ sudo service docker status (should see active (running)) $ sudo docker run hello-world From: Shashikanth vh [mailto:shashikanth...@huawei.com] Sent: Wednesday, October 25, 2017 1:47 PM To: Elhay Efrat <elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-s...@lists.onap.org<mailto:onap-s...@lists.onap.org> Subject: RE: [onap-discuss] [sdnc]could not able to see dockers running Thank you, ubuntu@vm1-sdnc:/opt$ docker version Client: Version: 17.05.0-ce API version: 1.29 Go version: go1.7.5 Git commit: 89658be Built: Thu May 4 22:06:06 2017 OS/Arch: linux/amd64 Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? ubuntu@vm1-sdnc:/opt$ sudo service docker status docker start/post-start, process 24348 post-start process 24349 ubuntu@vm1-sdnc:/opt$ From: Elhay Efrat [mailto:elhay.efr...@amdocs.com] Sent: 2017年10月25日 15:58 To: Shashikanth vh; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-s...@lists.onap.org<mailto:onap-s...@lists.onap.org> Subject: RE: [onap-discuss] [sdnc]could not able to see dockers running Could you please share service docker status ? ________________________________ From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> on behalf of Shashikanth vh Sent: Wednesday, October 25, 2017 10:23:33 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-s...@lists.onap.org<mailto:onap-s...@lists.onap.org> Subject: [onap-discuss] [sdnc]could not able to see dockers running Hi All, Trying to bring up SDNC using https://git.openstack.org/openstack-dev/devstack, after stack launch I could not execute docker ps command due to below error, required help to resolve this issue. ubuntu@vm1-sdnc:/opt$ ls config docker sdnc_install.sh sdnc_vm_init.sh ubuntu@vm1-sdnc:/opt$ docker ps Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Attached Heat template and envi file which I used to launch stack: Regards, Shashikanth. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
