dinker
rules_nixpkgs
| dinker | rules_nixpkgs | |
|---|---|---|
| 2 | 5 | |
| 12 | 269 | |
| - | 3.0% | |
| 10.0 | 9.0 | |
| 3 months ago | 6 days ago | |
| Go | Starlark | |
| ISC License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dinker
-
Crafting container images without Dockerfiles
(Self plug) I had the same thoughts as the author, and made this: https://github.com/andrewbaxter/dinker . Like stated in the article, if you're doing rust or go all you want is to dump the binary in the image. There's no reason to do the build inside the docker vm in that case, and it's super fast, and only uses dumb filesystem access - no daemons like docker, weird wip container managers like buildah, etc.
-
Rails on Docker · Fly
Self hoisting here, I put this together to make it easier to generate single (extra) layer docker images without needing a docker agent, capabilities, chroot, etc: https://github.com/andrewbaxter/dinker
Caveat: it doesn't work on Fly.io. They seem to be having some issue with OCI manifests: https://github.com/containers/skopeo/issues/1881 . They're also having issues with new docker versions pushing from CI: https://community.fly.io/t/deploying-to-fly-via-github-actio... ... the timing of this post seems weird.
FWIW the article says
> create a Docker image, also known as an OCI image
I don't think this is quite right. From my investigation, Docker and OCI images are basically content addressed trees, starting with a root manifest that points to other files and their hashes (root -> images -> layers -> layer configs + files). The OCI manifests and configs are separate to Docker manifests and configs and basically Docker will support both side by side.
rules_nixpkgs
- Crafting container images without Dockerfiles
-
Our Roadmap for Nix
I have spent a little bit of time working on a prototype of a setup like this, and have needed to write a lot of (hacky) glue and BUILD files.
I take it you have departed quite a bit from https://github.com/tweag/rules_nixpkgs ? Are you generating BUILD.bazel files for nixpkgs, or are you doing that by hand?
-
nix-shell, but make it lovely
I'm a fan of Tweag's rules_nixpkgs for bazel: https://github.com/tweag/rules_nixpkgs
-
Bazel 5.0 LTS with the new external dependency subsystem "Bzlmod"
Check out rules_nixpkgs as another way to get hermetic python. It does require that you install Nix, but everything else is driven from the Bazel side. Works for us on Linux and macos.
-
We Went All in on Sqlc/Pgx for Postgres and Go
Cool, thanks for the link.
For what it's worth, we use rules_nixpkgs to source Postgres (for Linux and Darwin) as well as things such as C and Python toolchains, and it's been working really well. It does require that the machine have Nix installed, though, but that opens up access to Nix's wide array of prebuilt packages.
https://github.com/tweag/rules_nixpkgs
What are some alternatives?
buildah - A tool that facilitates building OCI images.
bazel-skylib - Common useful functions and rules for Bazel
manifest-tool - Command line tool to create and query container image manifest list/indexes
pike - Generate CRUD gRPC backends from single YAML description.
bazel-nix-example
sqlc - Generate type-safe code from SQL
lamby - 🐑🛤 Simple Rails & AWS Lambda Integration
goyesql - Parse SQL files with multiple named queries and automatically prepare and scan them into structs.
nix2container - An archive-less dockerTools.buildImage implementation
sqlparser-rs - Extensible SQL Lexer and Parser for Rust
dockerfile-rails - Provides a Rails generator to produce Dockerfiles and related files.
SQLBoiler - Generate a Go ORM tailored to your database schema.