sdk-container-builds
dinker
sdk-container-builds | dinker | |
---|---|---|
7 | 2 | |
170 | 12 | |
1.2% | - | |
4.8 | 10.0 | |
6 days ago | 3 months ago | |
C# | Go | |
MIT License | ISC License |
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.
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.
What are some alternatives?
sdk-container-demo - Example projects and GitHub Actions Workflows using the .NET SDK to create containers
buildah - A tool that facilitates building OCI images.
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.
manifest-tool - Command line tool to create and query container image manifest list/indexes
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
bazel-nix-example
interactive - .NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
lamby - ๐๐ค Simple Rails & AWS Lambda Integration
conda-docker - Create minimal docker images from conda environments
nix2container - An archive-less dockerTools.buildImage implementation
dockerfile-rails - Provides a Rails generator to produce Dockerfiles and related files.
rules_nixpkgs - Rules for importing Nixpkgs packages into Bazel.