-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'NoneType' object is not iterable #4
Comments
Thanks for reporting this, @randyzwitch! I've heard this happen to a couple of people, but can't seem to repro myself. If your machine still exhibits this, any chance you can try running the following to help me narrow down the bug?
This will open a Bash shell within the
Does that behave? Go through without any exceptions being raised? If so, in the same interpreter, try the following:
Let me know if you can give it a shot. |
The problem is in the second snippet: >>> for image in client.images():
... print image['RepoTags']
...
[u'cloudera/clusterdock:latest']
None
[u'cloudera/clusterdock:cdh580_cm581_secondary-node']
[u'cloudera/clusterdock:cdh580_cm581_primary-node']
[u'hortonworks/ambari-server:latest']
[u'hortonworks/ambari-agent:latest']
[u'nginx:latest']
[u'sequenceiq/consul:v0.5.0-v6']
[u'sequenceiq/ambari:1.7.0']
[u'sequenceiq/ambari:1.6.0'] |
>>> for image in client.images():
... for tag in image['RepoTags']:
... print tag
...
cloudera/clusterdock:latest
Traceback (most recent call last):
File "<stdin>", line 2, in <module>
TypeError: 'NoneType' object is not iterable |
Ah ha! Got it, looks like there are instances where the Docker API does funny things. Let me put up a fix... Thanks @randyzwitch! |
Here's this if it helps, you can see which one has the
|
Just pushed an updated image, @randyzwitch. Can you give it a try to see if it fixed the issue? (Just rerun the command as before. The clusterdock helper script automatically pulls down new images.) |
Yes, that fixed it, thanks! |
Just cloned the newest version of clusterdock, fresh start of Docker on OSX:
The text was updated successfully, but these errors were encountered: