Marco seems to be a sudo issue? Are we running as root? Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308
From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ali, Shaheen Sent: Thursday, May 11, 2017 6:33 PM To: onap-discuss@lists.onap.org Cc: Ali, Shaheen <shaheen....@centurylink.com> Subject: [onap-discuss] (no subject) I just started the latest ONAP heat template and all the servers that depend on docker failed on the same line in their install.sh: Setting up docker-engine (17.05.0~ce-0~ubuntu-trusty) ... docker start/running, process 25003 Setting up cgroup-lite (1.9) ... cgroup-lite start/running Processing triggers for libc-bin (2.19-0ubuntu6.11) ... Processing triggers for ureadahead (0.100.0-16) ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 600 0 600 0 0 5839 0 --:--:-- --:--:-- --:--:-- 5882 100 7857k 100 7857k 0 0 3071k 0 0:00:02 0:00:02 --:--:-- 3722k docker stop/waiting start: Job failed to start Cloning into 'portal'... ... Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/ Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Notice the message: 'start: Job failed to start'. Have other people seen this problem? Is there a known work around or is there a fix in flight? Thanks, Shaheen This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
