busybox
kaniko
Our great sponsors
busybox | kaniko | |
---|---|---|
6 | 49 | |
55 | 13,925 | |
- | 2.3% | |
0.0 | 9.5 | |
about 5 years ago | 1 day ago | |
C | Go | |
GNU General Public License v3.0 or later | 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.
busybox
-
Sorry if this is too political.
Well.
- Guide: Hush Shell-Scripting Language
-
There's a tool to produce a diff-like output from c code?
Maybe you have better luck with the Busybox diff: https://github.com/brgl/busybox/blob/master/editors/diff.c
-
How could /dev/mem Linux directory be used in order to control the peripherals (MM/IO) ?
You can use busybox devmem to debug. The source code gives you an idea of how it works to write your own code.
-
Programming Puzzles
You can fairly easily spot things like recursive search tree implementations in the wild.
Also, compilers and interpreters often recursion, and that goes to as many levels as the program requires.
Have you heard of a "recursive descent parser"? GNU C++ uses one (a huge source file written in C++, well over a megabyte long). This will recurse as deeply as the program's nesting goes; C++ programs often go to more than three levels of nesting. (There are some non-recursive hacks mixed in there, like some operator precedence parsing involving an explicit stack: Shunting-Yard or similar?)
https://github.com/gcc-mirror/gcc/blob/master/gcc/cp/parser....
Let's switch over to embedded. Have you heard of BusyBox? BusyBox provides scaled down system utilities for embedded systems. It is very widely used.
BusyBox's "libb" internal library contains a function called "recursive_action" for walking file system trees. This is actually recursive, and frequently goes more than three levels deep in actual use:
https://github.com/brgl/busybox/blob/master/libbb/recursive_...
This is used by BusyBox programs like mdev (udev replacement) lsusb, lspci, chmod, ...
Also, HN isn't a good place to exhibit Lisp condescension/ignorance.
-
Go & secondary groups: a kaniko adventure!
This is almost the same implementation you see in busybox's id command source
kaniko
-
Using AKS for hosting ADO agent and using it to build and test as containers
If all you need to do is build container, you can use https://github.com/GoogleContainerTools/kaniko
-
Building Cages - Creating better DX for deploying Dockerfiles to AWS Nitro Enclaves
Kaniko for building the container images
-
Container and image vocabulary
kaniko
-
EKs 1.24 Docker issue
You should maybe look into Kaniko or use some other build tool
-
Schedule on Least Utilized Node
If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).
-
Are there tools you can use to improve your docker containers like Docker Slim?
Check out Kaniko for building containers https://github.com/GoogleContainerTools/kaniko . Only issue is it doesnt support windows containers.
-
You should use the OpenSSF Scorecard
It took less than 5 minutes to install. It quickly analysed the repo and identified easy ways to make the project more secure. Priya Wadhwa, Kaniko
-
Run Docker from within AWS Lambda?
I'd suggest to take a look at the Kaniko project, combined with custom container images in Lambda functions.
-
Faster Docker image builds in Cloud Build with layer caching
kaniko is a tool that allows you to build container images inside Kubernetes without the need for the Docker daemon. Effectively, it allows you to build Docker images without docker build.
-
Switching from docker-compose to k3s - what is needed ?
Kubernetes prefers to pull containers from registries. You may be able to work around it by specifying a local image in your Kube manifest. Both https://github.com/GoogleContainerTools/kaniko and/ or https://www.devspace.sh/ may help.
What are some alternatives?
barebox - The barebox bootloader - Mirror of ssh://[email protected]/barebox
podman - Podman: A tool for managing OCI containers and pods.
gcc
buildah - A tool that facilitates building OCI images.
stshell
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
hush - Hush is a unix shell based on the Lua programming language
jib - 🏗 Build container images for your Java applications.
hush - hush (a Bourne-style shell) for the GNO multitasking environment on the Apple IIgs
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
u-boot - "Das U-Boot" Source Tree
skopeo - Work with remote images registries - retrieving information, images, signing content