dinker
manifest-tool
| dinker | manifest-tool | |
|---|---|---|
| 2 | 2 | |
| 12 | 702 | |
| - | - | |
| 10.0 | 7.4 | |
| 3 months ago | 21 days ago | |
| Go | Go | |
| ISC 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.
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.
manifest-tool
- Crafting container images without Dockerfiles
-
rust-musl-cross docker images added linux/arm64 architecture support
Now we have multi-arch(amd64(aka. x86_64) and arm64(aka. aarch64)) docker images built using manifest-tool, it's should run much faster on Apple Silicon Mac than using qemu to run amd64 docker image.
What are some alternatives?
buildah - A tool that facilitates building OCI images.
umoci - umoci modifies Open Container images
bazel-nix-example
ormb - Docker for Your ML/DL Models Based on OCI Artifacts
lamby - 🐑🛤 Simple Rails & AWS Lambda Integration
saffire - [alpha] Controller to override image sources in the event that an image cannot be pulled.
nix2container - An archive-less dockerTools.buildImage implementation
rust-musl-cross - Docker images for compiling static Rust binaries using musl-cross
dockerfile-rails - Provides a Rails generator to produce Dockerfiles and related files.
go-containerregistry - Go library and CLIs for working with container registries
rules_nixpkgs - Rules for importing Nixpkgs packages into Bazel.
reg - Docker registry v2 command line client and repo listing generator with security checks.