top | item 13283851

Portainer, a UI for Docker

90 points| russmck | 9 years ago |media-glass.es | reply

28 comments

order
[+] kevan|9 years ago|reply
The lineage:

DockerUI - Created by Michael Crosby, later handed off to me when he got busy at Docker. The goal was to provide parity with the Docker command line, no extra features.

UI for Docker - Rename of the same project due to trademark concerns

Portainer - Fork of the original codebase with an expanded feature scope. I started losing interest in keeping up with Docker features when they added native Swarm, combined with a job change it was a good time to hand off the torch to someone else. It looks like they're trying to make a company out of it, I'm interested to see if they can make it happen.

[+] ncresswell|9 years ago|reply
Thanks Kevan, the work of Docker UI was legendary, however, as you pointed out, development slowed. We initially built portainer for our own internal use (as the UI for CloudInovasi.id), but liked it so much, we decided to focus on it. We are now wanting to add substantially more capability so that it becomes truly production ready. There will be a select few paid add-on's in the future for things like AD authentication, multi-tenancy etc, but the core will always be opensource and free.
[+] activatedgeek|9 years ago|reply
I'm not really sure on how this can move beyond a "good to have" UI on my dev machine. In production I'd always want a more wide-scoped dashboard like the one in K8s or Marathon.
[+] russmck|9 years ago|reply
The way I would look at it at the moment is that it provides a nice self-service interface allowing you give people access to deploy containers on dev servers which may free up time to allow you to concentrate on managing production.
[+] BrandonBradley|9 years ago|reply
This. I evaluated Portainer recently and found myself missing a few critical features available from Marathon.
[+] disiplus|9 years ago|reply
how is this different then shipyard -> https://shipyard-project.com/

i would love to be able to add docker-compose file and it would create everything for me ( something like rancher ). shipyard does not support this and with rancher i abounded it after running into problems.

[+] ncresswell|9 years ago|reply
We are adding support for compose YAML files in the Feb/March timeframe.. you will simply upload a yaml file, which portainer will then use to create containers/services
[+] mentat2737|9 years ago|reply
Why should I use this instead of Kubernetes?
[+] ralmeida|9 years ago|reply
As far as I understand, this is 'only' a UI layer on top of Docker and Docker Swarm. So this doesn't tackle any of the problems which Kubernetes (or Docker Swarm, for that matter) would, like scheduling and service discovery. Two very different things, really.
[+] hashkb|9 years ago|reply
Is there a similarly simple and rich UI for Kube?
[+] zemanel|9 years ago|reply
would love to see a curses (cli) based UI for managing images/containers (not aware of any).
[+] Walkman|9 years ago|reply
if you use docker from terminal, why would you need anything else than you have already? current docker commands are pretty easy and intuitive IMO.
[+] awt|9 years ago|reply
Can anyone point me to the best argument for hiding complexity instead of eliminating it?
[+] chillydawg|9 years ago|reply
Sometimes you want it (lots of config options) and sometimes you don't. In the real world, you need the detail available for strange edge cases but generally are happy with mostly-defaults.
[+] ncresswell|9 years ago|reply
We wanted portainer to mask the underlying complexity of Docker, without totally removing the functions that is making Docker legendary. Its a balancing act between hiding and removing compexity, but thats what makes UX design.
[+] lcalcote|9 years ago|reply
@ncresswell, more create and update capabilities would be great (e.g. the ability to create a network, connect a container, etc.)