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.

Kudos

Was able to set it up in under 30 seconds - kudos to you!

Really looking forward to the docker-compose support, though. I like the combination of docker-compose + traefik + labels. :)

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

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 see real time stats, do you have support for log retention?

Say I don't wanna ship logs elsewhere, can I define a retention period and check out logs locally?

ty

Will there be a OSX (MacOS) version? It's quite rare for software to have Windows and Linux support, but no OSX support.

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

Any plans to release a Mac version?