3 ms·

I really like Bazel (rules_oci) for building containers. It's the way building containers ""should"" be. Here's my base image, here's my files, here's my comm

I really like Bazel (rules_oci) for building containers. It's the way building containers ""should"" be. Here's my base image, here's my files, here's my command, write the into an image.

takeda 3y ago
That's pretty much how building on nix works, except you don't need base image or your application file, you specify what command to run from which package and it will be placed in the container with all runtime dependencies automatically. Of course you can customize the container further if needed.
- paulddraper 3y ago
  Yes, similar idea. With the objective of reproducible software. (Also, you don't need a base image for rules_oci either; most people choose to start with one.)
kmarc 3y ago
As many bazel rules, rules_oci's predecessor (rules_docker) was an unmaintained spagetti of hell, now we are pushed to rules_oci, and it's rpmtree recommended way of installing rpms which then in turn don't support post install script... All this bazel-is-our-savior complex burns down when we want to build a tiny bit complicated thing with it. And we unfortunately do try to do that (our devbox image), which with full caching takes long minutes to an hour, and it's a freaking thousands pine mess instead of using a lined dockerfioe with pinned versions. I absolutely hate bazel and its broken unmaintained Google-abandoned rulesets and I wish we either used either Docker or Buck2 for everything.
- paulddraper 3y ago
  > unmaintained spagetti of hell, 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.

I really like Bazel (rules_oci) for building containers. It's the way building containers ""should"" be. Here's my base image, here's my files, here's my command, write the into an image.

takeda 3y ago

That's pretty much how building on nix works, except you don't need base image or your application file, you specify what command to run from which package and it will be placed in the container with all runtime dependencies automatically. Of course you can customize the container further if needed.

paulddraper 3y ago
Yes, similar idea. With the objective of reproducible software. (Also, you don't need a base image for rules_oci either; most people choose to start with one.)

kmarc 3y ago

As many bazel rules, rules_oci's predecessor (rules_docker) was an unmaintained spagetti of hell, now we are pushed to rules_oci, and it's rpmtree recommended way of installing rpms which then in turn don't support post install script... All this bazel-is-our-savior complex burns down when we want to build a tiny bit complicated thing with it. And we unfortunately do try to do that (our devbox image), which with full caching takes long minutes to an hour, and it's a freaking thousands pine mess instead of using a lined dockerfioe with pinned versions. I absolutely hate bazel and its broken unmaintained Google-abandoned rulesets and I wish we either used either Docker or Buck2 for everything.

paulddraper 3y ago
> unmaintained spagetti of hell, 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.