Kitematic: Kitematic - Cannot find any local images

Created on 17 Mar 2017  Â·  4Comments  Â·  Source: docker/kitematic

Expected behavior

_Kitematic_ should display my local images. In the image management panel.

Actual behavior

_Kitematic_ reported _"Cannot find any local images"_ after I pulled additional ubuntu tagged images.

Information about the Issue

I had ubuntu:latest and pulled ubuntu:devel without issue. I then pulled ubuntu:17.04 (which has the same image ID, and I believe is the same image). Kitematic began showing error message.

When I looked at the images in the CLI I had the following ubuntu images:

I removed the untagged image and 17.04, and the problem corrected itself.

Steps to reproduce the behavior

  1. Pull ubuntu:latest and make a container, then stop it.
  2. Pull ubuntu:devel (I made and stopped another container).
  3. Pull ubuntu:17.04
  4. Check for error message in Kitematic, check for new untagged image in CLI.

Most helpful comment

I too was having this issue (was on v 0.12.0.0), but updating to the latest installer via @FrenchBen 's suggestion fixed it.

All 4 comments

What version of Kitematic/Docker are you using

The version from the .exe is 0.12.0.0 it's apparently an Alpha. I briefly
looked at updating it before sending this response however it appears that
Kitematic is now only available as a part of the docker toolbox. Is that
correct?

On Sat, Mar 18, 2017, 9:28 AM French Ben, notifications@github.com wrote:

What version of Kitematic/Docker are you using

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/kitematic/issues/2469#issuecomment-287486795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE3Rv6kWppjs5yhYzX-ahhD5GJUWxmFJks5rmwjugaJpZM4MgCc0
.

>

-- John Schram

@jangajack you can also download it (although with no installer) from this repo:
https://github.com/docker/kitematic/releases

I too was having this issue (was on v 0.12.0.0), but updating to the latest installer via @FrenchBen 's suggestion fixed it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Ashish0410verma picture Ashish0410verma  Â·  3Comments

EliotSlevin picture EliotSlevin  Â·  3Comments

rick02840 picture rick02840  Â·  3Comments

foverzar picture foverzar  Â·  4Comments

noahgift picture noahgift  Â·  3Comments