signalfx / maestro-ng

Orchestration of Docker-based, multi-host environments
https://signalfx.com
Apache License 2.0
683 stars 83 forks source link

ValueError: No JSON object could be decoded when starting with docker 1.3.0 #86

Closed rwestgeest closed 9 years ago

rwestgeest commented 10 years ago

I have upgraded docker (boot2docker) to 1.3. After that, maestro start and pull yield an error : "No JSON object could be decoded"

Can anyone hint towards the root cause of this. Is this a bug or some incompatibility issue?

Traceback (most recent call last): File "/Users/rob/Library/Python/2.7/lib/python/site-packages/maestro/main.py", line 200, in main getattr(c, options.command)(**vars(options)) File "/Users/rob/Library/Python/2.7/lib/python/site-packages/maestro/maestro.py", line 290, in start ignore_dependencies, concurrency)) File "/Users/rob/Library/Python/2.7/lib/python/site-packages/maestro/maestro.py", line 223, in _audit_play raise e

ValueError: No JSON object could be decoded

my test yaml:

name: SessionServer
registries:
ships:
  local:
    ip: '192.168.59.103'
    docker_port: 2376
    timeout: 60
services:
  registry:
    image: 'registry'
    instances:
      registry:
        ports: {cache_port: "5000:5000"}
        ship: local
rwestgeest commented 10 years ago

Seems to be a docker py issue as well. Docker 1.3.0 seems to enforce ssl for its api. see docker-py issue 365

mpetazzoni commented 9 years ago

This seems like it was a problem only with a certain combination of Docker daemon and docker-py and is unrelated to Maestro.