Live data from Hacker News

Show HN: Portainer – A lightweight management UI for Docker

portainer.io

11–20 of 53 posts

Re: Show HN: Portainer – A lightweight management UI for Docker

#11
Nice UI. But my mainproblem is not solved with an UI.

I did not understand who uses only default containers without configuration or only the small possible container configurations? For such people a default UI is perfect.

E.g. Containers with Linked Data-Containers to store the Data outside of a container, or setting up a container with different parameters (company/server specific). For such things i need an extra system which can not be used with your or any other UI.

We build our own small template system to manage Domains, Subdomains and the setup of the software within a container. How could this be connected to your UI?

It would be great if your Template-System will integrate an API, so really configurable Templates will be possible. Allow external Scripts, or better access to an Rest-Api to get configurations. This will be a huge advantage over other standard UIs.

Re: Show HN: Portainer – A lightweight management UI for Docker

#12
post #9

A similar project[1] which is also open source[2] and looks a lot similar. [1] https://shipyard-project.com/ [2] https://github.com/shipyard/shipyard

Well, it seems to cover the same functionality! But there is no windows support and does run in the shell instead of a docker image.

Re: Show HN: Portainer – A lightweight management UI for Docker

#13
post #8

Main developer here, feel free to ask any questions :)

We currently use DockerUI on our instances. What would be the compelling reason to switch to Portainer?

Our work is based on DockerUI, we do have a few extra features not implemented in DockerUI yet (container console for example), Swarm support and Portainer works well with Docker for Windows.

Re: Show HN: Portainer – A lightweight management UI for Docker

#14
post #9

A similar project[1] which is also open source[2] and looks a lot similar. [1] https://shipyard-project.com/ [2] https://github.com/shipyard/shipyard

Hey there ! We have a comparison table on our website: http://portainer.io/portainer-comparison.html

The main advantage against shipyard is that you only need to deploy one container to run Portainer, it's really simple and quick. Shipyard deployment is more complex.

Re: Show HN: Portainer – A lightweight management UI for Docker

#15
post #10

It looks absolutely amazing! Is it compatible with swarm mode? It would be awesome if it was a bit more explicit that it was running on a swarm/which node...

Thanks a lot ! It is indeed compatible with Swarm mode and allows you to manage your services. A lot of work is currently in progress on this part ! Feel free to try it and give use some feedback :)

Re: Show HN: Portainer – A lightweight management UI for Docker

#16
post #9

A similar project[1] which is also open source[2] and looks a lot similar. [1] https://shipyard-project.com/ [2] https://github.com/shipyard/shipyard

Cockpit [1] too, although that might be a bit more focused on single machine management than on clusters (don't use any of those - so I can't tell for sure)

[1] http://cockpit-project.org/

Re: Show HN: Portainer – A lightweight management UI for Docker

#18
post #4

Main developer here, feel free to ask any questions :)

Great work. Thanks. Do you have a roadmap for the future?

Our public roadmap is available here: https://github.com/portainer/portainer/projects/2

There's not so much content in it at the moment, but we plan to work on it this week :)

Re: Show HN: Portainer – A lightweight management UI for Docker

#19

Love the art style, love the site style, maybe useful as a desktop app for local development too perhaps?

Thanks ! A desktop app is not in the roadmap at the moment. Portainer is built to be easy to deploy and you just need to deploy one container to get it running so it can really be useful to manage local development environments :)

Re: Show HN: Portainer – A lightweight management UI for Docker

#20
post #11

Nice UI. But my mainproblem is not solved with an UI. I did not understand who uses only default containers without configuration or only the small possible container configurations? For such people a default UI is perfect. E.g. Containers with Linked Data-Containers to store the Data outside of a container, or setting up a container with different parameters (company/server specific). For such things i need an extra…

> E.g. Containers with Linked Data-Containers to store the Data outside of a container, or setting up a container with different parameters (company/server specific). For such things i need an extra system which can not be used with your or any other UI.

What ways are you injecting new data in? This service appears to support environment variables (which sounds right for setting up a container with different parameters) and volumes, do those not meet your needs? I'm always slightly hazy on the volumes-from data-container pattern so perhaps not.

Post reply on HN