source-to-image
buildkit
Our great sponsors
source-to-image | buildkit | |
---|---|---|
4 | 53 | |
2,424 | 7,669 | |
1.0% | 1.9% | |
6.5 | 9.8 | |
about 2 months ago | 4 days ago | |
Go | Go | |
Apache License 2.0 | 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.
source-to-image
-
Jenkins in kubernetes without docker
You can try and use s2i (source to image) - https://github.com/openshift/source-to-image You deploy container to your cluster that produce another image
-
Shipwright - Building Container Images In Kubernetes
Surprised to see it supports source-to-image (S2I). If you're using S2I, you're likely using OpenShift where your development pipeline is figured out for you. You wouldn't be using Shipwright on that platform.
-
Where can I find the IMG of version 2.0 of 351Elec?
If that's not an option, I unfortunately don't know how to compile source code into an IMG file from github, but I have a feeling that there's quite a few people who are knowledgeable in these matters lurking around this subreddit. The only thing I found was this: https://github.com/openshift/source-to-image but I have no idea how or where exactly to execute the code outlined in the readme below. Looks promising though.
-
It's Time to Say Goodbye to Docker
Source-To-Image (S2I) is a toolkit for building images directly from source code without Dockerfile. This tool works well for simple, expected scenarios and workflows but quickly becomes annoying and clumsy if you need little too much customization or if your project doesn't have the expected layout. You might consider using S2I if you are not very confident with Docker yet or if you build your images on OpenShift cluster, as builds with S2I are a built-in feature.
buildkit
- ARM vs x86 em Docker
-
The worst thing about Jenkins is that it works
> We are uding docker-in-docker at the moment
You can also run a "less privileged" container with all the features of Docker by using rootless buildkit in Kubernetes. Here are some examples:
https://github.com/moby/buildkit/tree/master/examples/kubern...
https://github.com/moby/buildkit/blob/master/examples/kubern...
It's also possible to run dedicated buildkitd workers and connect to them remotely.
-
Show HN: Dockerfile Explorer
- BuildOp evaluates its input as additional LLB operations to add to the graph to allow for dynamic build graphs (also unused in the Dockerfile frontend)
With the Dockerfile Explorer, we run the Dockerfile frontend[1] that BuildKit uses inside of WASM to parse and produce the LLB output locally in your browser. We then embed the Monaco Editor so that you can change your Dockerfile to see how it impacts the LLB output that BuildKit will use to build your Docker image.
You can see a quick video and read more details on how it all works here: https://depot.dev/blog/dockerfile-explorer.
We'd love any feedback or ideas folks would like around this type of tool!
[0] https://github.com/moby/buildkit#exploring-llb
- macOS Containers v0.0.1
-
Jenkins Agents On Kubernetes
Now since Kubernetes works off of containerd I'll be taking a different approach on handling container builds by using nerdctl and the buildkit that comes bundled with it. I'll do this on the amd64 control plane node since it's beefier than my Raspberry Pi workers for handling builds and build related services. Go ahead and download and unpack the latest nerdctl release as of writing (make sure to check the release page in case there's a new one):
-
Frequent Docker BuildKit cache misses with w/ multi-stage and docker-container
There's a 2-year-old moby/buildkit GitHub issue about frequent build cache misses when using the BuildKit docker-container driver and multi-stage builds. Anyone else in this sub run into this problem and/or have reasonable workarounds? It seems like something that should come up pretty often.
-
A Panic in BuildKit: an Open Source Journey
A couple months ago I encountered a bug in buildkit - when enabling OpenTelemetry tracing, we got occasional panics. With a bit of investigation, we found the cause, fixed and tested in our fork and internal deployments, and pushed to upstream.
-
Is it possible to copy files from a manifest in Dockerfile?
I do some search in the internet and there seems to be no good solution, so I just create a feature request: https://github.com/moby/buildkit/issues/3859
-
Cicada - CI/CD platform written with Rust
Yeah, only Linux containers at the moment, BuildKit is the way we are constructing pipelines and doing caching. Split on if we will support non-linux hosts, but definitely want to find a good solution to not doing Docker-in-Docker.
-
Better support of Docker layer caching in Cargo
Relevant issues are https://github.com/moby/buildkit/issues/3011 and https://github.com/moby/buildkit/issues/1512.
What are some alternatives?
kaniko - Build Container Images In Kubernetes
buildah - A tool that facilitates building OCI images.
skopeo - Work with remote images registries - retrieving information, images, signing content
jib - 🏗 Build container images for your Java applications.
351ELEC - Handheld firmware optimized for the Anbernic RG351P/M/V devices.
buildx - Docker CLI plugin for extended build capabilities with BuildKit
Bazel - a fast, scalable, multi-language and extensible build system
podman - Podman: A tool for managing OCI containers and pods.
jenkins-std-lib - Bringing the Zen of Python to Jenkins.
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...