Closed rwestgeest closed 9 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
This seems like it was a problem only with a certain combination of Docker daemon and docker-py
and is unrelated to Maestro.
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: