sdk-container-builds
nixery
sdk-container-builds | nixery | |
---|---|---|
7 | 18 | |
170 | 1,695 | |
1.2% | - | |
4.8 | 4.8 | |
6 days ago | 3 months ago | |
C# | Go | |
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.
nixery
- Way to get NVM working in CI/CD systems
-
What's your favourite Docker Image, and why?
The ones from https://nixery.dev/
-
k8s docker image with basic troubleshooting tools
You can build your own with https://nixery.dev/
-
Crafting container images without Dockerfiles
I built a service for doing this ad-hoc via image names a few years ago and it enjoys some popularity with CI & debugging use-cases: https://nixery.dev/
-
Nixpacks takes a source directory and produces an OCI compliant image
name is eerily similar to `nixpkgs`, i.e. the monorepo that defines all packages and one of the underlying technologies here. i get the play on buildpacks, but still, as a nix user it makes me do a double take reading the name
this is neat though, and in political terms, the elevator pitch mentions nix itself as an implementation detail in passing. hopefully, if this catches on, it'll function as a non-threatening gateway drug to nix itself, when users inevitably go digging into the weeds
for anyone interested, prior art on the nix container front: https://nixery.dev
-
Ask HN: Have You Left Kubernetes?
Wow, this is excellent! At a previous job, we had been using k8s + knative to spin up containers on demand, and likewise were unhappy with the delays. Spawner seems excellent.
One question: have you had to do any custom container builds on demand, and if so, have you had to deal with large containers (e.g. a Python base image with a few larger packages installed from PyPI)? We would run up against extremely long build image times using tools like kaniko, and caching would typically have only a limited benefit.
I was experimenting using Nix to maybe solve some of these problems, but never got far enough to run a speed test, and then left the job before finishing. But it seems to me some sort of algorithm like Nixery uses (https://nixery.dev) to generate cacheable layers with completely repeatable builds and nothing extraneous would help.
Maybe that's not a problem you had to solve, but if it is, I'd love your thoughts.
-
Hacker News top posts: Apr 19, 2022
Nixery – Docker images on the fly with Nix\ (38 comments)
- Nixery – Docker images on the fly with Nix