Brian_D1
2 Bronze

ECS Single Node Installation Problem

I'm posting a support question for another person who is encountering a problem when installing the ECS software from Github.  Any assistance is appreciated.

======================================

Okay, after discovering that docker doesn’t respect bashrc, I added the proxy info in its config and tried again.  New error:

Pulling repository emccorp/ecs-software

6a34c2f5a3b5: Error pulling image (latest) from emccorp/ecs-software, Driver devicemapper failed to create image rootfs 8a37be8b91b22e3ddc279d454d80f44c858b3978ff7cdd6759115c54bec01f9f: Error running DeviceCreate (createSnapDevice) dm_task_run faFATA[0001] Error pulling image (latest) from emccorp/ecs-software, Driver devicemapper failed to create image rootfs 8a37be8b91b22e3ddc279d454d80f44c858b3978ff7cdd6759115c54bec01f9f: Error running DeviceCreate (createSnapDevice) dm_task_run failed

Docker ps shows no container.  Here is the rest. There is one blurb about this that appears related/unrelated and specific to EMC’s internal network:  https://community.emc.com/thread/216216

I think I’m done troubleshooting the install until after vmworld.  Please have some feedback for what I might be doing wrong.

[28/Aug/2015 20:45:17] INFO [root:425] Check the Docker processes.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

[28/Aug/2015 20:45:17] INFO [root:449] Backup object properties file

FATA[0000] Error response from daemon: No such container: ecsstandalone

[28/Aug/2015 20:45:17] INFO [root:453] Backup application config file

FATA[0000] Error response from daemon: No such container: ecsstandalone

[28/Aug/2015 20:45:17] INFO [root:457] Copy object properties file to host

FATA[0000] Error response from daemon: No such container: ecsstandalone

[28/Aug/2015 20:45:17] INFO [root:461] Copy application config file to host

FATA[0000] Error response from daemon: No such container: ecsstandalone

[28/Aug/2015 20:45:17] INFO [root:465] Modify BlobSvc config for single node

sh: /host/cm.object.properties1: No such file or directory

[28/Aug/2015 20:45:17] INFO [root:469] Modify Portal config for to bypass validation

[28/Aug/2015 20:45:17] INFO [root:472] Copy modified files to container

FATA[0000] Error response from daemon: No such container: ecsstandalone

FATA[0000] Error response from daemon: No such container: ecsstandalone

[28/Aug/2015 20:45:17] INFO [root:478] Stop container

Error response from daemon: No such container: ecsstandalone

FATA[0000] Error: failed to stop one or more containers

[28/Aug/2015 20:45:17] INFO [root:481] Start container

Error response from daemon: No such container: ecsstandalone

FATA[0000] Error: failed to start one or more containers

[28/Aug/2015 20:45:17] INFO [root:484] Clean up local files

Traceback (most recent call last):

  File "step1_ecs_singlenode_install.py", line 659, in <module>

    main()

  File "step1_ecs_singlenode_install.py", line 651, in main

getAuthToken(ip_address,root,ChangeMe)

NameError: global name 'root' is not defined

[root@ospoc103 ecs-single-node]#

[root@ospoc103 ecs-single-node]# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

0 Kudos
1 Reply
Aaron_Peterson
2 Bronze

Re: ECS Single Node Installation Problem

Hi, Brian,

This seems to be an issue related to Docker running out of disk space. A few general solutions which seem to work for others include simply waiting and retrying to pull the image, removing the contents of your /var/lib/docker directory and restarting your Docker instance (be sure to save anything crucial first!), or setting DOCKER_STORAGE_OPTIONS in /etc/sysconfig/docker-storage to an empty value.

If these don't work for your instance, you may want to take a look at the contents of /var/lib/docker/devicemapper/devicemapper/metadata; see if there are any apparent errors, and if so we can address them more directly.

As the NameError you're seeing near the bottom, that's an issue with the install file that has since been resolved - replacing your version of step1_ecs_singlenode_install.py with the most recent version should prevent the error in the future.

- Aaron

0 Kudos