dimgx only shows topmost layer of image

[edmorley]

Hi! Thank you for a great tool - I was hunting for ages for something like this and about to write my own when I came across it.

However I believe it's not working with newer versions of Docker, perhaps due to the changes described here?
http://windsock.io/explaining-docker-image-ids/

For example:

$ docker --version
Docker version 17.05.0-ce, build 89658be

$ dimgx --version
dimgx v0.2.4

$ docker pull ubuntu:16.04
16.04: Pulling from library/ubuntu
...
Status: Downloaded newer image for ubuntu:16.04

$ docker history ubuntu:16.04
IMAGE               CREATED             CREATED BY                                      SIZE
        COMMENT
d355ed3537e9        3 days ago          /bin/sh -c #(nop)  CMD ["/bin/bash"]            0B
<missing>           3 days ago          /bin/sh -c mkdir -p /run/systemd && echo '...   7B
<missing>           3 days ago          /bin/sh -c sed -i 's/^#\s*\(deb.*universe\...   2.76kB
<missing>           3 days ago          /bin/sh -c rm -rf /var/lib/apt/lists/*          0B
<missing>           3 days ago          /bin/sh -c set -xe   && echo '#!/bin/sh' >...   745B
<missing>           3 days ago          /bin/sh -c #(nop) ADD file:c251a21fbe3a651...   119MB

$ dimgx ubuntu:16.04
REPO TAG                IMAGE ID        PARENT ID       CREATED         LAYER SIZE      VIRTUAL SIZE
ubuntu:16.04            sha256:d355e    -               3 days ago      119.2 MB        119.2 MB

$ dimgx -l 0:3 ubuntu:16.04
WARNING : "0" does not resolve to any layer associated with image "ubuntu:16.04"
WARNING : "3" does not resolve to any layer associated with image "ubuntu:16.04"
WARNING : no known layers selected
REPO TAG                IMAGE ID        PARENT ID       CREATED         LAYER SIZE      VIRTUAL SIZE

...whereas I would have expected the output from the first dimgx command to contain more than one entry, and to roughly mirror the output from docker history, and the second command to not result in errors.

[posita]

Hi @edmorley! Thanks for the well articulated issue report. Unfortunately, I've kind of let this tool languish for a while, having not used it with recent versions of Docker. However, if you're at all familiar with Python and the Docker SDK, I'm very open to modifications/pull requests if you're willing to try to attempt a fix.

Please let me know if you need more guidance in this area.

Thanks again, and my sincere apologies for the delay in my response.