-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
_get_legacy_containers_iter() TypeError: argument of type 'NoneType' is not iterable #1694
Comments
Which docker version are you using? In docker 1.6 "no labels" is an empty mapping, but this errors seems like it's returning |
My docker version:
I suspect this pull is related: #1643 |
Can confirm the same behaviour -
|
Suggest simply prefixing the erroneous conditional on the last frame of that stacktrace (compose/legacy.py:152) with |
Seeing this with |
Can also confirm this same behavior with |
I think the easy fix is to change Maybe this behaviour differs based on the version of docker that was used to create the container? Do you happen to know if the old containers were created with a version of docker < 1.6 ? A paste of the |
I'm seeing this and I think had a set of container that I upgraded to labels with the |
Got a fix in #1705, but agree - it'd be good to know where/why the API is doing this. |
Could anyone who's experiencing this issue please give one of these binaries a try? If they fix the problem, I'll release 1.3.3. Mac: http://cl.ly/0N2g0J0r2a25/docker-compose-Darwin-x86_64 |
Yep, works a treat for me thanks.
|
Thanks @aanand Docker-compose for Linux-x86_64 works for me |
Great. This fix is now in Compose 1.3.3 - please update: https://github.com/docker/compose/releases/tag/1.3.3 |
Thank you! this worked great. |
Thanks @aanand, works perfectly! |
.. which fixed docker/compose#1694
I've come to this as I got the same error in
even with minimal .yml file I tried the newer version, and I'm getting the error:
I updated all the images, the problem still exists. |
I'm getting this error (or at least a very similar one) with docker-compose 1.3.3 with docker 1.6.2 (on circleci):
|
@d3ming That doesn't look similar to me - it looks like a connection error (specifically, a timeout). |
@aanand ah OK - I was looking from the top of the callstack and it looked similar but I see whaty ou mean now. Any other insight from the callstack? (like what is it trying to connect to when it fails)? Should this be treated as a separate bug? |
@d3ming It looks like it happened when performing the API call to create a container. I don't know if we can stop it from happening, because I don't know what's causing it - it could be a transient networking issue on your end. In any case, it's definitely a separate issue, yes. |
Got it - opened #1923 |
I'm getting this with docker-compose up
The docker-compose.yml is like
The version of docker-compose is:
|
.. which fixed docker/compose#1694
I just upgraded from 1.1.0 to 1.3.2, and after dealing with the /tmp directory being mounted as noexec (issue #1339), I ran into another issue that I couldn't find in the backlog;
Downgrading to 1.3.1 seems to alleviate this behavior.
The text was updated successfully, but these errors were encountered: