Go to file
Anthony Lapenna 0f51cb66e0 Rdash theme integration (#1)
* Adding latest build to dist.

* Adding latest build to dist.

* Bump other app version.

* Build latest changes.

* Bump version to 0.7.0.

* Version bump to 0.9.0-beta and remote API 1.20.

* Whoah there, back down to 0.8.0-beta.

* Merge branch 'crosbymichael-master' into crosbymichael-dist

* Add volume options in volume creation form

* display swarm cluster information in Swarm tab

* update LICENSE

* update repository URL in status bar

* remove console logs

* do not display Swarm containers anywhere in the UI

* update position for add/remove option on Volumes page

* compliant with swarm == 1.2.0 API support

* update nginx-basic-auth examples with latest nginx and swarm example

* Updated .gitignore

* update .gitignore

* reverted entry for dist/uifordocker in .gitignore

* WIP

* fix linter issues

* added logo

* update repository URL

* update .gitignore (ignore dist/*)

* add lodash

* add containers actions binding (start, stop...)

* replace image icon

* bind remove image action

* bind network remove action

* bind volume remove action

* update logo

* wip on container details

* update logo scaling, favicon and page title

* wip container view

* add containers actions in container view

* add image view

* add network view

* remove useless data in tables

* add pull image, create network modals

* add create volume modal

* update style for createVolume options

* add start container modal

* create volume modal now use a select to display drivers

* add container stats

* add containerTop view in stats view

* fix trimcontainername filter

* add container logs view

* updated .gitignore

* remove useless files/modules

* remove useless chart in image view

* replace $location usage with $state.go

* remove useless swarm example
2016-06-02 17:34:03 +12:00
app Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
assets Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
dist Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
examples/nginx-basic-auth Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
test/unit Fix spec for top view. 2016-02-15 23:49:20 -06:00
.dockerignore Added docker-compose config for nginx-basic-auth. 2015-12-17 01:31:07 -06:00
.gitignore Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
.godir Makes dockerui compatible with dokku 2013-12-09 00:26:01 +00:00
Dockerfile DockerUI => UI For Docker 2016-04-29 21:57:27 -05:00
LICENSE Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
Procfile Makes dockerui compatible with dokku 2013-12-09 00:26:01 +00:00
README.md DockerUI => UI For Docker 2016-04-29 21:57:27 -05:00
bower.json Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
container.png Initial commit 2013-06-08 15:12:14 -09:00
containers.png Initial commit 2013-06-08 15:12:14 -09:00
dockerui-checksum.txt Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
dockerui.go DockerUI => UI For Docker 2016-04-29 21:57:27 -05:00
gruntFile.js Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
index.html Rdash theme integration (#1) 2016-06-02 17:34:03 +12:00
package.json DockerUI => UI For Docker 2016-04-29 21:57:27 -05:00

README.md

UI For Docker

Containers UI For Docker is a web interface for the Docker Remote API. The goal is to provide a pure client side implementation so it is effortless to connect and manage docker.

Container

Goals

  • Minimal dependencies - I really want to keep this project a pure html/js app.
  • Consistency - The web UI should be consistent with the commands found on the docker CLI.

Quickstart

  1. Run: docker run -d -p 9000:9000 --privileged -v /var/run/docker.sock:/var/run/docker.sock uifd/ui-for-docker

  2. Open your browser to http://<dockerd host ip>:9000

Bind mounting the Unix socket into the UI For Docker container is much more secure than exposing your docker daemon over TCP. The --privileged flag is required for hosts using SELinux. You should still secure your UI For Docker instance behind some type of auth. Directions for using Nginx auth are here.

Specify socket to connect to Docker daemon

By default UI For Docker connects to the Docker daemon with/var/run/docker.sock. For this to work you need to bind mount the unix socket into the container with -v /var/run/docker.sock:/var/run/docker.sock.

You can use the -e flag to change this socket:

# Connect to a tcp socket:
$ docker run -d -p 9000:9000 --privileged uifd/ui-for-docker -e http://127.0.0.1:2375

Change address/port UI For Docker is served on

UI For Docker listens on port 9000 by default. If you run UI For Docker inside a container then you can bind the container's internal port to any external address and port:

# Expose UI For Docker on 10.20.30.1:80
$ docker run -d -p 10.20.30.1:80:9000 --privileged -v /var/run/docker.sock:/var/run/docker.sock uifd/ui-for-docker

Check the wiki for more info about using UI For Docker

Stack

Todo:

  • Full repository support
  • Search
  • Push files to a container
  • Unit tests

License - MIT

The UI For Docker code is licensed under the MIT license.

UI For Docker: Copyright (c) 2013-2016 Michael Crosby (crosbymichael.com), Kevan Ahlquist (kevanahlquist.com)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.