So, here's a concern for you: this provides for a severe security hole, since it has the ability to effectively run as root on any machine its connected to (a'la privileged mode, volumes, network, leaking secrets through environment variables). It might be worthwhile to find a way to mitigate that security hole, or add some serious access control restrictions.
I wouldn't be too surprised if your test cluster machines are frequently rooted.
Saw it, loved it, installed in only 30 seconds, now using it in production. There are definitely issues to be resolved but I believe most of them are simple enough for single commits.
It should be noted that this project still lacks proper access management. There is no authentication either. You can set up Basic Auth but it feels dirty in my opinion. Guard it behind your firewall if you are gonna use it in production.
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.
We used DockerUI as our initial inspiration and codebase, but have added so many more features, and make it so much cleaner... If you are using DockerUI, then switching to portainer should be an easy choice
Thanks! I started using it on two machines already, no problems so far. It's great that it runs from a single Docker container without any stupid "curl | sudo bash" scripts.
I tried the instructions for Linux on a Mac: https://portainer.readthedocs.io/en/latest/deployment.html#c....
(I'm guessing the developers simply haven't tested on Mac)
So far, it seems to work. My guess is that the developers haven't had a chance to test on a Mac and just don't want to make any claims just yet.
This is awesome ! Indeed we don't have any Mac and so we did not have the possibility to try it. We'll ask a few Mac users to give it a go before claiming Mac support. Thanks a lot !
