Go to file
Anthony Lapenna 739a5ec299 fix(general): fix the size display using the filesize library (#246)
* fix(general): fix the size display using the filesize library

* refactor(humansize): use default value for filter
2016-10-01 21:38:20 +13:00
api chore(version): bump version number 2016-09-24 22:33:23 +12:00
app fix(general): fix the size display using the filesize library (#246) 2016-10-01 21:38:20 +13:00
assets style(favicon): update favicon (#242) 2016-10-01 16:51:45 +13:00
test/unit fix(general): fix the size display using the filesize library (#246) 2016-10-01 21:38:20 +13:00
.dockerignore
.gitignore docs(project): new documentation (#229) 2016-09-24 22:31:37 +12:00
.godir
CONTRIBUTING.md
Dockerfile
LICENSE
README.md docs(README): update README 2016-09-30 18:51:55 +13:00
bower.json fix(general): fix the size display using the filesize library (#246) 2016-10-01 21:38:20 +13:00
gruntFile.js fix(general): fix the size display using the filesize library (#246) 2016-10-01 21:38:20 +13:00
index.html
package.json chore(version): bump version number 2016-09-24 22:33:23 +12:00

README.md

Portainer

The easiest way to manage Docker.

Microbadger Documentation Status Gitter

Portainer is a lightweight management UI which allows you to easily manage your Docker host or Swarm cluster.

Usage

It's really simple to deploy it using Docker:

$ docker run -d -p 9000:9000 portainer/portainer -H tcp://<DOCKER_HOST>:<DOCKER_PORT>

Just point it at your targeted Docker host and then access Portainer by hitting http://localhost:9000 with a web browser.

If your target is a Docker Swarm cluster or a Docker cluster using swarm mode, just add the flag --swarm:

$ docker run -d -p 9000:9000 portainer/portainer -H tcp://<SWARM_HOST>:<SWARM_PORT> --swarm

If you don't specify any target, its default behaviour is to use a bind mount on the Docker socket so you can easily deploy it to manage your local Docker host:

$ docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer

Have a look at our documentation for more deployment options.

Configuration

Portainer is easy to tune using CLI flags.

Hiding specific containers

Portainer allows you to hide container with a specific label by using the -l flag.

For example, take a container started with the label owner=acme:

$ docker run -d --label owner=acme nginx

Simply add the -l owner=acme option on the CLI when starting Portainer:

$ docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer -l owner=acme

Use your own templates

Portainer allows you to rapidly deploy containers using App Templates.

By default Portainer templates will be used but you can also define your own templates.

Add the --templates flag and specify the external location of your templates when starting Portainer:

$ docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer --templates http://my-host.my-domain/templates.json

For more information about hosting your own template definitions and the format, see the templates documentation.

Check our documentation for more configuration options.

FAQ

Be sure to check our FAQ if you are missing some information.

Limitations

Portainer has full support for the following Docker versions:

  • Docker 1.10 to Docker 1.12 (including swarm-mode)
  • Docker Swarm >= 1.2.3

Partial support for the following Docker versions (some features may not be available):

  • Docker 1.9