rules_docker was fundamentally flawed -- and overreaching in scope -- in ways that rules_oci is not.
> broken unmaintained Google-abandoned rulesets
rules_oci last commit was 12 hours ago, and it's been actively maintained for years.
(This criticism is even weirder from someone pushing Buck2. Like, it's a great tool. But, apparently it warranted a complete rewrite too, eh?)
> instead of using a lined dockerfioe with pinned versions
You'll pin every transitive version?
> All this bazel-is-our-savior complex burns down when we want to build a tiny bit complicated thing with it.
Let me rephrase. I would not use Bazel to build images from rpm or deb packages.
But....would you use Nix for installing rpm or deb packages????? I believe you've lost the thread.
rules_docker was fundamentally flawed -- and overreaching in scope -- in ways that rules_oci is not.
> broken unmaintained Google-abandoned rulesets
rules_oci last commit was 12 hours ago, and it's been actively maintained for years.
(This criticism is even weirder from someone pushing Buck2. Like, it's a great tool. But, apparently it warranted a complete rewrite too, eh?)
> instead of using a lined dockerfioe with pinned versions
You'll pin every transitive version?
> All this bazel-is-our-savior complex burns down when we want to build a tiny bit complicated thing with it.
Let me rephrase. I would not use Bazel to build images from rpm or deb packages.
But....would you use Nix for installing rpm or deb packages????? I believe you've lost the thread.