Hi Neal, thanks for sharing! On Wed, Apr 8, 2020 at 1:05 AM Neal Gompa <ngompa13@gmail.com> wrote:
Hey all,
I don't know if any of y'all saw this yet, but Docker, Inc. has announced[1] this new thing called the "Compose Specification[2]". It looks like they're attempting to generalize the Docker Compose format for broader use.
What do you folks think of it?
I like that the spec is about to be opened as it gives compose a fair chance for the future. It is a rather common request for Podman to support compose and while I do not know of plans to integrate it into Podman's code base (compose is a *lot* of code), there is podman-compose [3] developed by the community. With the upcoming new rest API [4], we will likely be able to support docker-compose by pointing it to the Podman socket. Ultimately, I would love everybody to use podman-play-kube on their machines but I understand that a lot of folks depend on docker-compose and migration is not always an option. I don't feel ready to interpret the strategy behind opening the spec yet though. In my personal experience, Docker was very protective and defensive when I tried to contribute features which left me sceptical. However, lot's of things have changed at Docker and maybe there's a new genuine interest in being more open. In other words, I like it :-) but I don't fully understand the motivation yet. Thanks for reaching out! Kind regards, Valentin [3] https://github.com/containers/podman-compose [4] https://podman.io/blogs/2020/01/17/podman-new-api.html
[1]: https://www.docker.com/blog/announcing-the-compose-specification/ [2]: https://www.compose-spec.io/
-- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io