Supplement containers with metadata from `docker inspect`

[mvanveen]

[mvanveen]

docker-py returns objects with a schema similar to the following when you run the containers function on a client:

[
   {
      "Ports" : "49155->8000",
      "SizeRw" : 0,
      "Command" : "python -m SimpleHTTPServer",
      "Id" : "b575c9ece1b9e9001a4685a1df3a831e92790b0feffc8fe8a392fd9e53905df6",
      "Status" : "Up 6 hours",
      "Created" : 1376188514,
      "Image" : "885f960143a5",
      "SizeRootFs" : 0
   },
   {
      "Ports" : "49154->8000",
      "SizeRw" : 0,
      "Command" : "python -m SimpleHTTPServer",
      "Id" : "b225c9398c4b50ee96b9359cc3290bf846a1f0bbe0e6c330ee3fd69666268919",
      "Status" : "Up 6 hours",
      "Created" : 1376188085,
      "Image" : "885f960143a5",
      "SizeRootFs" : 0
   }
]

But this is only part of the picture. You can get a lot more metadata with docker inspect <containerid>:

[{
    "ID": "b575c9ece1b9e9001a4685a1df3a831e92790b0feffc8fe8a392fd9e53905df6",
    "Created": "2013-08-11T02:35:14.841392768Z",
    "Path": "python",
    "Args": [
        "-m",
        "SimpleHTTPServer"
    ],
    "Config": {
        "Hostname": "b575c9ece1b9",
        "User": "",
        "Memory": 0,
        "MemorySwap": 0,
        "CpuShares": 0,
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "PortSpecs": [
            "8000"
        ],
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": null,
        "Cmd": [
            "python",
            "-m",
            "SimpleHTTPServer"
        ],
        "Dns": null,
        "Image": "885f960143a5",
        "Volumes": {},
        "VolumesFrom": "",
        "Entrypoint": []
    },
    "State": {
        "Running": true,
        "Pid": 1762,
        "ExitCode": 0,
        "StartedAt": "2013-08-11T02:35:38.347052671Z",
        "Ghost": false
    },
    "Image": "885f960143a5e489ac0cb11900a3f15237ff634094bc5374d83e6a358da2e588",
    "NetworkSettings": {
        "IPAddress": "172.16.42.4",
        "IPPrefixLen": 24,
        "Gateway": "172.16.42.1",
        "Bridge": "docker0",
        "PortMapping": {
            "Tcp": {
                "8000": "49155"
            },
            "Udp": {}
        }
    },
    "SysInitPath": "/usr/bin/docker",
    "ResolvConfPath": "/etc/resolv.conf",
    "Volumes": {},
    "VolumesRW": {}
}]

The final published container object spec is going to need to include at least some this metadata, and probably also have getters for getting to it if the metadata in question isn't directly an attribute on the container object.