Hi,

great extension, I use it on a regular basis. But, isn't there always a but :-), I miss the "name" column in the "Container Running" list.

I've a bunch of Jenkins docker container running and I can only distinguish between them by the port, even they have "speaking" names.

Would be a nice enhancement.

Thanks and Cheers,
Alex

PS: A Refresh Icon would be nice too :-)

Great tool!

Is it possible to add any statistic about server load in realtime? I'm using a "remote" docker daemon on a linux server and working on my pc only with the docker client.

Could be usefull to monitor CPU/RAM/HDD on the daemon server.

Carlo

I have 3 web server containers running, it would be nice to see the name of the container.

Thank you for a nice app

The second chrome app (that doesn't work very well) have a docker registry browser. This would be a very nice addition to this app.

Apologies for lack of screenshot.

I can point Docker UI to a Swarm master node on the swarm API port (3376), but it seems to only partially work.

The Home page lists version as "swarm/1.0.0 (api: 1.21). There should be three containers, all running, but running containers shows 0. All containers does show 3 as expected.

The Containers page reports "Unable to connect"

The Images page appears to work fine.

I can connect to each swarm node separately, as well as the swarm master on vanilla Docker API port (2376) and everything works as expected (minus unrelated issues already raised in other tickets).

So is Docker swarm supposed to be supported yet, or is it just coincidence that a few bits appear to work already?

Would be nice if the dashboard supported the native docker tcp socket on docker and swarm.

Now, it errors:
"Unable to connect to http://192.168.26.11:4000, is Boot2docker/docker-machine running?"

App connects, able to view available images and deploy, but am unable to view running containers

I am on Ubuntu 16.04 Desktop with Docker version 1.11.1. I followed the instructions on the wiki to set up for a system running systemd at https://github.com/felixgborrego/docker-ui-chrome-app/wiki/linux and all seemed to go well. (systemd shows everything running as expected)

When I try http://localhost:2375/_ping in a browser I receive "OK". However, if I drop the ending and simply enter http://localhost:2375 I get a 404 error. (Also tried the machine IP as well as 127.0.0.1)

When I open the Simple Docker UI app the Containers, Images, and Settings tabs all work fine despite the 404 error in the browser and the Home tab.

I'm relatively new to Docker, so not sure what info I can provide you to help figure this out. A web search didn't yield much luck.

NOTE: I am able to install images, and run containers just fine, via CLI or the Simple Docker UI.

A very nice enhancement would be to allow the user to edit the container properties, like the command, the environment, working dir, volume mapping.

view image.

What is the license of your app? could you add licence information as file or headers on each source file?

I am using docker-machine on Linux/Ubuntu and couldn't setup the certificates properly.

The docker-ui-chrome-app works like a charm without https however that breaks docker-machine...

I tried following the steps on the wiki for OSX and Linux, issue #21 without success.

Specifically this part:

• First, make Chrome trust in the auto-generated CA. Execute this command to add the new CA to your Certificate Trust Settings in your Keychain:

  security add-trusted-cert -k ~/Library/Keychains/login.keychain ~/.docker/machine/certs/ca.pem

• Also, you need to add the auto-generated certificate to your Keychain:

  security import ~/.docker/machine/certs/key.pem -k ~/Library/Keychains/login.keychain

  security import ~/.docker/machine/certs/cert.pem -k ~/Library/Keychains/login.keychain

I added those keys to the Gnome keyring application but not sure of the exact command line...

Would be great to have this enchancement when I click on the >_docker... commands below. Or to have another button "copy to clipboard" rather than to select & ctrl-c.

On line 225 of DockerClient.scala file you use

val ws = schema + substringAfter(s"$url/containers/$containerId/attach/ws?logs=1&stderr=1&stdout=1&stream=1&stdin=1", "://")

I supose you use this service to atach container to docker-ui container console

here you are using logs flag set to _true_ (defaults is false)

This brings all historic logs from the container.
The problem i find here, is getting all log history in containers that generate a great amount of logs, as gitlab container, when i try to start it from docker-ui i get stuck for a while until i can press start button.
Could be more usefull manage both functionalities in a diferent way.

• one to atach console to container without log history, as when u attach to a container from command line
• another to visualize logs through service GET /containers/(id or name)/logs

Another option is give the posibility of visualize logs or not.

I know you want keep your app simple, so may not be a great idea, in any case just want tell you as a sugestion

Best regards and thanks for your great work

Hey,
I have put my docker remote api behind a nginx reverse proxy (configured via ssl with basic auth).
But this makes Simple Docker UI unable to access the remote api...
When I disable basic auth, I can connect to the api, but I don't want this open without credentials...
Could you please change this?

Best Regards,

The terminal seems to be flakey - the first container I ran (bortels/rubydev which is my generic ruby dev environment) showed the irb prompt, but no keyboard input worked. Killing that and starting again just shows [Connected], without the prompt or keyboard working. Tried a few different variants, down to something as simple as busybox. Killed it, restarted, same behavior (no prompt at all in the terminal).

Environment: OS X Yoemite, boot2docker 1.4.1, docker client version 5. Upgrading to boot2docker 1.5 has the same issue.

PS. This looks really really nice. Thank you for sharing.

Cant find anything on SSL support?
Would be great to be able to add key and certificate when connecting to the docker API :)

Is it possible for Docker UI to deploy a new container?

Shows only the images. For the pages Home and Containers says "Unable to connect".
Environment:
Server: Ubuntu 15.04, Docker 1.7.0
Client: Chrome 43.0.2357.130 m, Simple Docker UI (Beta) 0.1.2

At least on MacOS, the preferred path is to use docker-machine (instead of boot2docker). Changes to the documentation on the Settings section would be sufficient.

There is incorrect size for sum of containers and images in case of many big containers and images. Perhaps this is only an Integer overflow? Suggestion is to convert the summarized size to MB, GB, TB based on size.

I am on docker version 1.7.1 and API v 1.17.
On a VM running ~40 containers the Home and Containers tab take 2+ minutes to load.

Specifically following API spikes CPU usage of docker daemon process

/v1.17/containers/json?all=false&size=true

Removing size returns results instantaneously.

my docker daemon admin serivce is bound to "-H tcp://192.168.100.10:1234"

this chrom app for windows can connect to it
but this chrome app in my mac can not connect to it

When I scroll inside the console till the end, its window is as wide as the browser window (ever wider and crosses the border on the right). See 1.png.
When I scroll inside the console up, its windows gets shrinked and the text is wrapped. See 2.png.

Would be great to have always same width console window (as wide as the browser) and to have another scroll bar inside the console window.

The possibility to remove Docker images would a nice feature.

According to this ...

• boot2docker/boot2docker#589

I think you should use "export DOCKER_TLS=no" in your profile not just "DOCKER_TLS=no"

But the export is missing from this wiki page:

• https://github.com/felixgborrego/docker-ui-chrome-app/wiki/windows

Currently you can only attach to terminal, and see File system changes in container instances. Would be great if there's a tab for std/err.

Hello,

First, thanks for this app, this was what i searched.

Is is possible to link the account with https://hub.docker.com/stars/ to get starred containers and add the star from the app ?

Thanks for this cool app

After selecting the repository i would like to clone. It started to clone.
But when i want to stop the pulling. I cant stop it.

Im using chrome 44, Ubuntu 14.04

This is a great app! Wow!
But what about security?

How can I make sure that public_ip:2375 can only used by my own ip/hostname?
OS: Ubuntu 14.04
Docker: 1.9.1

It would be nice to be able to open a Dockerfile on my hard drive and have the image created.

When deploying a container, the user can click on Ports and then Custom. A list of ports is displayed. The Host Ports are blank. Please change the default to be the same as the Container port.

I know virtually nothing about chrome apps, so this may be completely idiotic, but a very quick look at the source looks like it could be possible to just generate the files to be deployable.

Would it be possible to generate this as a webapp in a docker container that any HTML5 browser could use?

Just a thought.

Hi,

i'm unable to connect to the swarm cluster : Unable to connect to http://swarm-master-ip:4000, is Docker daemon running?

however is possible with standard docker api

Bye

While on the create window, if you select the tabs for "Volumes" or "Environments", you can no longer access the port mapping function.

Solution could be to consider that a tab.

No issue, just wanted to say thanks and great work. I just started using it and may have some suggestions down the road, but for now...

AWESOME!

When there are many logs would need a scroll in the terminal to see all content. It happens that an exception is raised but I can not see it complete because the terminal does not have scroll.

In the Docker console, "docker images" shows tagged and untagged images. In this Docker Chrome app, only the tagged images are shown. Please make all images visible.

the new docker osx whcih uses docker.local as the xhyve instnace to run docker fails to verify

Love docker ui but there are still a couple of things that make me have to use the cli; linking containers, setting system variables and port forwards. If these things could be managed from within Docker Ui it would have all important basic docker features and would completely replace the CLI for the average user.

Hello,
It would be nice to be able to change the default value for environment variables and volumes on the "run" command.
Thanks

In Images tab there is no info about inactive images (e.g. I can't remove them from UI)
Also in Home screen the counter shows number of active images. These images with REPOSITORY and TAG marked as are unmanageable from UI

I have the following management url:
http://admin:[email protected]:5555

which uses basic auth to access, and it works fine.

but the open ports are incorrectly linked:
(suppose it's an apache 8080:80)
instead of myhost.com:8080
I have "admin:8080" as a link.

thanks, dan

It would be nice to be able to connect to multiple docker instances.

I'm on Linux, I just installed this Chrome App, I followed the installation wizard (http://localhost:4243/_ping give me an OK). But when I start the application, nothing happens and the current tab (in which I started the Docker UI) is closed.

Could add an interanl description field for the container? So the users have the possibility to share certain infomations about the container.

I have been testing your Docker UI Chrome app and have been really impressed with it.
One item I was looking for that I did not see was a place to add / do volume mapping when starting up a container.
Is there any chance you will be adding that ability with a button / section like there is for "Ports".
Or
Any chance there can be an additional "command" box that will enter switches before the name of the image is called and then volumes could be mapped that way as well.

Thanks
--Tom

hi, I was wondering how are the ports to be mapped chosen? For example if a container exposes "8043" and I choose "all" to be mapped, you (or docker maybe) randomly selects ports on the host, right?

It would be great if the ports were the same as in the container by default (if available), as this would make the container transparent.

maybe related: #52

cheers, dan

The date of creation and sometimes the image size are badly wrapped: