sdk-container-builds
buildah
sdk-container-builds | buildah | |
---|---|---|
7 | 26 | |
170 | 7,037 | |
1.2% | 1.3% | |
4.8 | 9.6 | |
6 days ago | 4 days 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.
buildah
-
A gopher’s journey to the center of container images
For the task of building the graph image, my first idea was to rely on buildah. In fact, our design was already heavily relying on containers/image for all things regarding copying images from one registry to the other, or from one registry to an archive. The obvious choice was to use the same suite of modules in order to keep dependencies to a minimum.
-
Podman Desktop for Java Development
I appreciate that podman can run daemonless, but I've gotten tired of waiting for them to implement heredoc support and have continued to use docker.
-
How to use Podman inside of a container
You do realize that, under the hood, buildah uses a container engine (runc by default)? See https://github.com/containers/buildah/blob/main/docs/buildah...
-
Container and image vocabulary
buildah
-
How to use Buildah to create a build-service written in golang
I found this small tutorial: https://github.com/containers/buildah/blob/main/docs/tutorials/04-include-in-your-build-tool.md and it works.
-
From code to customers in just 13 seconds.
# https://github.com/containers/buildah/issues/3666 volume /var/lib/containers
-
Podman v4.4, Buildah v1.29 released!
Last week, Buildah version 1.29 was also released. The prune command has been added to clean intermediate images as well as the build and mount cache. Support for the –group-add option to the from and build commands was added. One useful feature of this, it to use the –group-add keep-groups option, which allows rootless users to take advantage of their group access to file and devices mounted into the build containers. And the –cache-from and –cache-to options for the build command now allow for multiple sources. This can be used to improve the speed of builds, especially in CI/CD environments.
- Crafting container images without Dockerfiles
-
Rails on Docker · Fly
Unfortunately this syntax is not generally supported yet - it's only supported with the buildkit backend and only landed in the 1.3 "labs" release. It was moved to stable in early 2022 (see https://github.com/moby/buildkit/issues/2574), so that seems to be better, but I think may still require a syntax directive to enable.
Many other dockerfile build tools still don't support it, e.g. buildah (see https://github.com/containers/buildah/issues/3474)
Useful now if you have control over the environment your images are being built in, but I'm excited to the future where it's commonplace!
-
Container Deep Dive 2: Container Engines
For more information regarding the bundled tools see: CRI tools.