Kitematic: Containers created on CLI are not being displayed in Kitematic

[kbowerma]

I think this should be possible but I can't figure out how to do. I want images/containers that I have built to show up the gui.

I tried opening the terminal and building a images and did not see it. Then I started the container but still did not see it. Is this not supported?

Thanks great work so far this is awesome so far

[jmorganca]

Hi there! Thanks for creating an issue.

Kitematic syncs with what you do on the CLI as long as commands are run while pointed at the right Docker VM & ENgine. To make sure your shell is correctly either use:

• $(docker-machine env dev) in a terminal or click the Docker Terminal button in Kitematic:

Or click on the button shown below:

Does this work at all?

In terms of being able to build an image in Kitematic - that's not yet possible - sorry.

[kykim]

Having the same issue.

I opened the Docker Terminal by clicking the button as describe, created an image, then created a container. It's running. But it doesn't appear in the Kitematic window.

[mchiang0610]

@kykim Do you have the procedure to help us reproduce on our side?

Thanks!

[themotu]

@mchiang0610 same for me

docker run -d -t -p 8282:80 -p 443:443 -v /Users/me/work/drupal_docker/logs:/var/log/apache2 -v /Users/me/work/drupal_docker/status:/var/www/html/status status

starts a container
4868fd8d79b7 status:latest "/bin/sh -c 'bash -C 2 minutes ago Up 2 minutes 0.0.0.0:443->443/tcp, 3306/tcp, 0.0.0.0:8282->80/tcp prickly_bardeen

and then kitematic doesn't show the created container. I built the container from the command line after clicking "Open terminal to use docker command line"

Kitematic version: 0.5.27

[d3v1an7]

:+1:

Was working in 0.7.7, but containers no longer show in 0.8.5.

All containers were created and started via command line.
I have this in .bash_profile and .bashrc:

if [ $(type -P docker-machine) ]; then eval $(docker-machine env dev); fi

[FrenchBen]

@d3v1an7 the VM that kitematic uses is called 'default' - Change your .bashrc to:

if [ $(type -P docker-machine) ]; then eval $(docker-machine env default); fi 

[klousiaj]

:+1: I'm having the same problem.

Kitematic 0.9.4
El Capitan 10.11.2

Locally built image on the command line started through the Kitematic GUI. Start the container via the CLI with a docker run and the container is not shown in the Kitematic container list.

c99873e9eaf6 klousiaj/wso2-das:1.0 "/bin/sh -c 'sh ./wso" 3 hours ago Up 3 hours 7711/tcp, 8243/tcp, 8280/tcp, 9443/tcp, 9763/tcp, 10397/tcp condescending_easley

[FrenchBen]

@klousiaj anyway to share the Dockerfile (and assets) for this image? I'd like to try and replicate this.

[klousiaj]

I haven't identified a pattern with a particular Dockerfile/image. I have a couple of published images that you can find source for on my github. But it doesn't seem that my problem is limited to only images built locally through the CLI.

It was working for a while. I restarted and am seeing the following now:

CONTAINER ID	IMAGE	COMMAND	CREATED	STATUS	PORTS	NAMES
27024cb47b35	klousiaj/wso2-das:latest	"/bin/sh -c 'sh ./wso"	3 minutes ago	Up 23 seconds	0.0.0.0:32774->7611/tcp, 0.0.0.0:32773->7711/tcp, 0.0.0.0:32772->9160/tcp, 0.0.0.0:32771->9443/tcp, 0.0.0.0:32770->9763/tcp, 0.0.0.0:32769->21000/tcp	wso2-das
2cfc4f6ce786	mysql:latest	"/entrypoint.sh mysql"	6 minutes ago	Up 2 minutes	0.0.0.0:3306->3306/tcp	mysql
901d8abae64c	klousiaj/h2-db:latest	"/bin/sh -c 'java -cp"	2 days ago	Exited (143) 44 hours ago		h2-db
8e2d37681ce8	klousiaj/wso2-am:latest	"/bin/sh -c 'sh ./wso"	3 days ago	Exited (137) 2 hours ago		wso2-am
7b865d931290	centos:7	"bash"	4 days ago	Exited (0) 4 days ago		cranky_wright

I'm not sure where my other containers went...

[FrenchBen]

OK great - last question for my qa, can you provide the commands you run with each?
docker build -t klousiaj/wso2-das:latest . ?
docker run -itd --name wso2 klousiaj/wso2-das:latest ?

[klousiaj]

You got it...

I was able to just bring the UI back up inline. I'm thinking that this might be an issue with processes not all dying in sync. I went into Activity Monitor and force killed a couple of docker-machine processes and the next start of Kitematic brought it all back up in line. (I will say, this no longer seems related to the OP's issue)

[FrenchBen]

seems something else is happening in the background. Thanks for the update. I'll close this issue as it's becoming unrelated.

Would you mind creating a new issue for this (keeping the OP from getting a bunch of emails)

[fenglianxu]

I have seen the same issue but if you click refresh container list from the view menu, you will see all of the running container in Kitematic UI.

[pranavgarg]

If you are on mac and have the native docker and somehow it was showing earlier and all of a sudden one day you don't see the containers in kitematic. Then check the kitematic settings ->VM settings-> Use VirtualBox instead of Native on next restart is checked. Uncheck it and it will show all the containers.

[hotdang-ca]

I had to turn ON that feature (it was off), and on kitematic restart, turn it back off.

Once that was done, we were good.

[btwq]

Thanks @hotdang-ca's suggestion worked for me too

[leosco]

Why is this issue closed? This is basic behavior that needs to be supported by default. If you pull a docker image from a non-Docker Hub source, you lose all the functionality of Kitematic!

[leosco]

@pranavgarg If I do that, it breaks my Kitematic, telling me to install Docker Toolbox. I follow the link, and it tells me that Docker Toolbox is deprecated and that I shouldn't use it.

Also the download link is broken https://docs.docker.com/toolbox/toolbox_install_mac/

I had to reinstall to fix it...

[456wyc]

我遇到了同样的问题，看了大家的问题，我尝试把 kitematic 退出后再启动，然后就可以看到列表了。可能是重启电脑后，自动打开原来的窗口引起的。