conda-docker
dinker
| conda-docker | dinker | |
|---|---|---|
| 1 | 2 | |
| 60 | 12 | |
| - | - | |
| 0.0 | 10.0 | |
| 9 months ago | 3 months ago | |
| Python | Go | |
| BSD 3-clause "New" or "Revised" 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.
conda-docker
-
Crafting container images without Dockerfiles
For creating images without docker from conda/mamba environments, there's also the existing `conda-docker` tool https://github.com/conda-incubator/conda-docker.
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?
apko - Build OCI images from APK packages directly without Dockerfile
buildah - A tool that facilitates building OCI images.
rules_docker - Rules for building and handling Docker images with Bazel
manifest-tool - Command line tool to create and query container image manifest list/indexes
bazel-nix-example
crane - A Nix library for building cargo projects. Never build twice thanks to incremental artifact caching.
lamby - 🐑🛤 Simple Rails & AWS Lambda Integration
nix-ci
nix2container - An archive-less dockerTools.buildImage implementation
dockerfile-rails - Provides a Rails generator to produce Dockerfiles and related files.