3 ms·

That's not "forcing", it's choosing what you ship and especially (since RHEL is a paid product) for what software you're willing to spend money on customer supp

That's not "forcing", it's choosing what you ship and especially (since RHEL is a paid product) for what software you're willing to spend money on customer support and feature requests. Fedora has always had Docker and on RHEL you could install it with community support only.

sofixa 2y ago
> That's not "forcing", it's choosing what you ship and especially (since RHEL is a paid product) for what software you're willing to spend money on customer support and feature requests. That's forcing an alternative, inferior in terms of features, tool. Canonical were publicly criticised for switching the Firefox apt release to a Snap for their easier maintenance.. Red Hat replacing Docker and telling everyone it' replaced by Podman, even if Podman could do 1/3 of what Docker could, is pretty similar. And they did the same with the whole ecosystem - buildah is another example of them reinventing the wheel because they just had to. Kaniko exists and works well. Docker build has downsides. But Red Hat just had to build their own one too.
- bonzini 2y ago
  It's giving an alternative that you can support to your paying customers, over one where you have found out after 5 years of contributions that you weren't welcome. Yes it was inferior but the alternative was nothing at all. Should I remind you of the Docker people showing up at a conference with "I say no to systemd PRs" t-shirts (https://lwn.net/Articles/676938/ https://lwn.net/Articles/676938/)? Also, Kaniko was made public in January 2018. Buildah had its first release in February 2018. It's unfortunate that both exist but so is life, they were developed concurrently even though Kaniko came first by a few weeks. Given the previous experience with Docker I am not surprised they chose to build something integrated with podman.

3 ms·

That's not "forcing", it's choosing what you ship and especially (since RHEL is a paid product) for what software you're willing to spend money on customer supp

by bonzini 2y ago

sofixa 2y ago
> That's not "forcing", it's choosing what you ship and especially (since RHEL is a paid product) for what software you're willing to spend money on customer support and feature requests. That's forcing an alternative, inferior in terms of features, tool. Canonical were publicly criticised for switching the Firefox apt release to a Snap for their easier maintenance.. Red Hat replacing Docker and telling everyone it' replaced by Podman, even if Podman could do 1/3 of what Docker could, is pretty similar. And they did the same with the whole ecosystem - buildah is another example of them reinventing the wheel because they just had to. Kaniko exists and works well. Docker build has downsides. But Red Hat just had to build their own one too.
- bonzini 2y ago
  It's giving an alternative that you can support to your paying customers, over one where you have found out after 5 years of contributions that you weren't welcome. Yes it was inferior but the alternative was nothing at all. Should I remind you of the Docker people showing up at a conference with "I say no to systemd PRs" t-shirts (https://lwn.net/Articles/676938/ https://lwn.net/Articles/676938/)? Also, Kaniko was made public in January 2018. Buildah had its first release in February 2018. It's unfortunate that both exist but so is life, they were developed concurrently even though Kaniko came first by a few weeks. Given the previous experience with Docker I am not surprised they chose to build something integrated with podman.