1 min read
Ok, I think I'm annoyed (not sure, but almost).
They always said,
"develop against docker api, it will not change."
"Docker run" is just an api call to a server, you can replace the server with a cluster master"
And now, how do you deploy? "docker service create"...
Is all my work around docker-compose compatible? "Yes, we have a crappy and unstable converter!"
Then there is this converter also compose2kube :) I'm sure it is as good, and if I have to switch, I'll switch for the big guys :)
They also have kpm which looks interesting!
And ceph and git support for volumes \o/
In this battle, my position was always to wait with my docker-compose (looking at the less energy consuming path). But @docker, if I have to work to migrate existing compose to whatever, I'll change for the winner!
Go Fork yourself Docker!