21–30 of 31 posts
Can anyone point me to the best argument for hiding complexity instead of eliminating it?
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.
would love to see a curses (cli) based UI for managing images/containers (not aware of any).
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.
Can anyone point me to the best argument for hiding complexity instead of eliminating it?
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.
This. I evaluated Portainer recently and found myself missing a few critical features available from Marathon.
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.
Why should I use this instead of Kubernetes?
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.
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, comb…
Earlier quoted context omitted.
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.
We are adding "tasks or jobs" in Feb/March timeframe, which will allow you to schedule any portainer task (such as scaling up or down a service). Swarmmode really does make service discovery a lot simpler, no need for Consul etc.