export stack file from Docker Cloud

[anas-aso]

I exported the current running stackfiles from Docker Cloud account and I got a file with all the indentations missed up

[tifayuki]

@anas-aso Which OS are you on? I tested it on both OS X and Ubuntu, and it works fine.

[anas-aso]

@tifayuki I'm using OS X 10.11.3 (15D21) I wanted to try it again now and I got this famous error message :

$ docker-cloud stack ls
Status 429 (GET https://cloud.docker.com/api/tutum/v1/auth/). Response: {"detail": "Too many login attempts."}

[fermayo]

@anas-aso can you please provide the exported docker-compose that you get?

[anas-aso]

@fermayo there is nothing special about it, but here it is :

lb:
  image: 'dockercloud/haproxy:1.0.1'
  autoredeploy: true
  links:
    - web-site
  ports:
    - '80:80'
    - '443:443'
  restart: always
  roles:
    - global
  sequential_deployment: true
web-site:
  image: 'tutum/hello-world:latest'
  autoredeploy: true
  restart: always
  sequential_deployment: true

and this is what I got after exporting it from Docker Cloud

lb:
  autoredeploy: true
  image: dockercloud/haproxy:1.0.1
  links:
  - web-site
  ports:
  - 80:80
  - 443:443
  restart: always
  roles:
  - global
  sequential_deployment: true
web-site:
  autoredeploy: true
  image: tutum/hello-world:latest
  restart: always
  sequential_deployment: true

You see here that the indentation was missed up for links, ports and roles values and this is the docker-cloud version I'm using :

$ docker-cloud --version
docker-cloud 1.0.1

[fermayo]

So that indentation meets the YAML spec, so should work everywhere. Do you have any problem loading that?

[anas-aso]

yeah, you are right. Actually I have a local setup where I test stack files with docker-compose before pushing them to Docker Cloud (of course all docker cloud related service configuration are removed before) and for some reason docker-compose was complaining about this indentation which is not the case anymore. I'm not sure if this has something to do with docker machine on OS X or not, but it seems like the issue disappeared after a reboot ! Anyway, thanks for following with me. I will close this issue now

[fermayo]

Thanks for letting us know :)