Data container state not being reflected appropriately

[kkebb]

Hello again!

Your tool is amazing, and am loving it's seamless integration with the docker commands. It just came to my attention that it seems that when we define data containers in the YAML file and run a status check against the container, we see that the container is marked as "down for " in red, instead of the status being marked as N/A, or a more appropriate label for the status of a data container. Example:

data:
    image: busybox
    instances:
      data1:
        ship: boot2docker
        container_volumes:
          - /path/to/dir

RESULT:

  #  INSTANCE                                 SERVICE              SHIP                                     CONTAINER                  STATUS    
  1. data1                                    data                 boot2docker                              latest:51106c7             down for 5s

[mpetazzoni]

Yep Maestro doesn't do much in the way of supporting data containers. A lot of assumptions revolve around the presence of some kind of running service within the container, or for the container to be Running as per Docker, as opposed to just being present.

Fixing this would take some time, but I'll think about it.

[kkebb]

Cool, thanks for your prompt reply!

[iangkent]

I think this would be a good feature as well. Some of the people operating our deployments using maestro-ng are confused by the red states of data containers and think there is a problem.