sdk-container-builds
rules_nixpkgs
sdk-container-builds | rules_nixpkgs | |
---|---|---|
7 | 5 | |
170 | 269 | |
1.2% | 3.0% | |
4.8 | 9.0 | |
6 days ago | 3 days ago | |
C# | Starlark | |
MIT 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.
sdk-container-builds
-
.NET 8 Standalone 50% Smaller On Linux
You can also publish .NET apps/services directly as container images [1].
Or you can distribute them as a single file, standalone, "ready to run" application, which precompiles your methods and includes the JIT. This results in a larger executable, but keeps all the functionality, including reflection and runtime code generation, intact.
And, of course, you can install .NET core directly on your Linux system, just as you would for Python or Ruby (where you also don't usually rely on the default installation).
[1] https://learn.microsoft.com/en-us/dotnet/core/docker/publish...
-
Secure your .NET cloud apps with rootless Linux Containers
If you're using the https://github.com/dotnet/sdk-container-builds tech to build containers, we're working on a 0.4 version of that package that applies this rootless user by default - the goal is that the SDK tooling is the smoothest, least-effort pathway to secure, correct, best-practice containers for all .NET applications!
-
Dockerize .NET Applications without Dockerfile! - Built-In Container Support for .NET 7
Alternatively, here's Microsoft's own documentation about how to do all of the above: https://github.com/dotnet/sdk-container-builds/blob/main/docs/GettingStarted.md
-
Crafting container images without Dockerfiles
We've been baking this functionality directly into the .NET SDK for a couple releases now: https://github.com/dotnet/sdk-container-builds
It's really nice to derive mostly-complete container images from information your build system already has available, and the speed/UX benefits are great too!
-
Announcing built-in container support for the .NET SDK
Funny you should mention scaffolding out a Dockerfile - internally we'd been talking about that as a bridge to other services that are highly Dockerfile-based. I just logged https://github.com/dotnet/sdk-container-builds/issues/146 to track this request. We likely won't prioritize it for the 7.0 release unless we get huge amounts of feedback that it would be helpful, but it is something we'd like to do.
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