@roberthbailey will handle this one.

FYI, Docker is also contemplating GC of unreachable images:
https://botbot.me/freenode/docker-dev/2014-07-11/?msg=17856832&page=3

That shouldn't stop us from doing something, but we should prioritize complementary functionality.

Ping on this. It really makes things difficult when your stuff is crashlooping.

This is slowly percolating to the top of my TODO list. ETA to start on it is before end of the week.

I've written a small cli program that gets the output of ListContainers using the go docker remote api to see all of the dead and alive containers (this is the same output as 'docker ps -a'). Unfortunately, it looks like the only way to tell the status of a container is to use string parsing, as the status field is something like "Up 3 seconds" or "Exited (0) 53 minutes ago" rather than an actual type. This is going to be fragile.

You should be able to look at the 'inspect' output for each container, no?

"State": {
    "ExitCode": 0,
    "FinishedAt": "2014-08-12T05:52:38.116285958Z",
    "Paused": false,
    "Pid": 0,
    "Running": false,
    "StartedAt": "2014-08-12T05:52:36.592949946Z"
},

On Wed, Sep 3, 2014 at 3:16 PM, roberthbailey notifications@github.com
wrote:

I've written a small cli program that gets the output of ListContainers
using the go docker remote api to see all of the dead and alive containers
(this is the same output as 'docker ps -a'). Unfortunately, it looks like
the only way to tell the status of a container is to use string parsing, as
the status field is something like "Up 3 seconds" or "Exited (0) 53 minutes
ago" rather than an actual type. This is going to be fragile.

Reply to this email directly or view it on GitHub
#157 (comment)
.

That sounds much better than what I was seeing. Let me give it a try...

Is this being actively pursued? Should it be reassigned?

Not currently being pursued. Feel free to reassign.

This should be closed by #2022, yes?

@ryaneleary That only addressed containers, not images.

I am reopening this issue since I believe #3097 doesn't address image gc issue. See #3264 for detail reasons. In a short version, current support of gc of image depending on docker's "dangling=true", which gives us proper unused images on a node. Instead it only returns a list of image layers without tag.

Created #5457 and assigned to myself.