nix-portable
go-containerregistry
nix-portable | go-containerregistry | |
---|---|---|
11 | 17 | |
752 | 3,006 | |
- | 1.2% | |
7.8 | 6.8 | |
3 days ago | about 20 hours ago | |
Nix | 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.
nix-portable
-
An independent package manager that every hacker deserves
There is also nix-portable (https://github.com/DavHau/nix-portable), which is basically a drop-in replacement for normal nix that does everything required for no-root operation by itself when needed. Just put the single binary in your PATH and it's ready.
-
Docker's deleting Open Source images and here's what you need to know
level (/nix/store/)
Yes, for cache hits to happen it has to be this way as far as I remember.
There is a project called nix-portable though that I've seen some HPC users report success with:
https://github.com/DavHau/nix-portable
-
The Determinate Nix Installer
Great work Graham and team, I'll be switching to it on OSX.
I wonder if you took a look at some of the modifications done by portable-nix (https://github.com/DavHau/nix-portable), most important ones being:
a) Allowing user to choose the location of the nix folder (for example $HOME/.nix) by using bwrap or proot
- is it possible to install the nix package manager with no root privleges?
-
Day 15 with silverblue, loving how rock stable the whole system feels! Exactly the kind of distro i've always wanted.
you can install it and forget about it. yeah the major downside is that you need to disable selinux unless you use nix portable.
- I found this
-
I made a nix-portable integration for direnv for my friend who doesn't want to install nix on his machine 😈
Yeah sadly nix-portable doesn't support macOS because of missing kernel features. They are also thinking about docker fallback though: https://github.com/DavHau/nix-portable/issues/23 🤔😋
-
Introducing Riff, a Nix-based tool for automatically providing external dependencies to Rust projects
There is this: https://github.com/DavHau/nix-portable but I agree we need an official solution
-
We want to make Nix better
Not entirely true, there are many ways in which you can use a custom location and still take advantage of the binary cache. You can do it with chroot, file system namespaces, bind mounts and so on. There's also a nice user friendly tool that does exactly this [1].
[1]: https://github.com/DavHau/nix-portable
-
Nix Development Container
This is cool! In a similar vein, it's worth mentioning nix-portable is a thing. Same idea of containerization except it avoids docker. https://github.com/DavHau/nix-portable
go-containerregistry
-
A gopher’s journey to the center of container images
I also explored another module, go-containerregistry, in order to build images without root privileges. The approach is completely different, and we can manipulate each component of the container image separately. This can present an advantage, if you're looking for a way to fine tune things.
-
Skip build if "${CI_REGISTRY_IMAGE}:${CI_COMMIT_SHORT_SHA}" exists on container registry
Use crane ls in a different job to check the tags in the registry. Create an artifact from its output that you evaluate in your kaniko job to check if the build should run or not.
-
Docker: We’re No Longer Sunsetting the Free Team Plan
Multi-arch builds are easy to "transfer" IMHO
crane cp docker.io/openfaas/gateway:0.10.0 ghcr.io/openfaas/gateway:0.10.0
If you've not used it yet - do take a look. Crane doesn't pull the images into a local Docker library for re-tagging and re-pushing.
https://github.com/google/go-containerregistry/blob/main/cmd...
-
Weekly: This Week I Learned (TWIL?) thread
crane - tool to copy images from one repo to another - https://github.com/google/go-containerregistry/blob/main/cmd/crane/doc/crane.md
- Dockerhub to (likely?) delete a lot of organizations.
-
FYI: Docker is deleting Open Source organisations
pretty sure the crane being referred by alex is this one: https://github.com/google/go-containerregistry/tree/main/cmd/crane
-
Docker's deleting Open Source images and here's what you need to know
https://github.com/google/go-containerregistry/tree/main/cmd...
It was recommended in this article:
-
Crafting container images without Dockerfiles
This is one of my absolute favorite topics. Pardon me while I rant and self-promote :D
Dockerfiles are great for flexibility, and have been a critical contributor to the adoption of Docker containers. It's very easy to take a base image, add a thing to it, and publish your version.
Unfortunately Dockerfiles are also full of gotchas and opaque cargo-culted best practices to avoid them. Being an open-ended execution environment, it's basically impossible to tell even during the build what's being added to the image, which has downstream implications for anybody trying to get an SBOM from the image for example.
Instead, I contribute to a number of tools to build and manage images without Dockerfiles. Each of them are less featureful than Dockerfiles, but being more constrained in what they can do, you can get a lot more visibility into what they're doing, since they're not able to do "whatever the user wants".
1. https://github.com/google/go-containerregistry is a Go module to interact with images in the registry and in tarballs and layouts, in the local docker daemon. You can append layers, squash layers, modify metadata, etc.
2. crane is a CLI that uses the above (in the same repo) to make many of the same modifications from the commandline. `crane append` for instance adds a layer containing some contents to an image, entirely in the registry, without even pulling the base image.
3. ko (https://ko.build) is a tool to build Go applications into images without Dockerfiles or Docker at all. It runs `go build`, appends that binary on top of a base image, and pushes it directly to the registry. It generates an SBOM declaring what Go modules went into the app it put into the image, since that's all it can do.
4. apko (https://apko.dev) is a tool to assemble an image from pre-built apks, without Docker. It's capable of producing "distroless" images easily with config in YAML. It generates an SBOM declaring exactly what apks it put in the image, since that's all it can do.
Bazel's rules_docker is another contender in the space, and GCP's distroless images use it to place Debian .debs into an image. Apko is its spiritual successor, and uses YAML instead of Bazel's own config language, which makes it a lot easier to adopt and use (IMO), with all of the same benefits.
I'm excited to see more folks realizing that Dockerfiles aren't always necessary, and can sometimes make your life harder. I'm extra excited to see more tools and tutorials digging into the details of how container images work, and preaching the gospel that they can be built and modified using existing tooling and relatively simple libraries. Excellent article!
-
ImagePullPolicy: IfNotPresent - (image doesn’t exist in repo) - Is it possible to pull the micro service image from an EKS node and then push to repo?
Look at using tools like skopeo or crane
-
Containerd... Do I use Docker to build the container image? I miss the Docker Shim
Pretty much any tool works: docker, podman, kaniko, crane(if you're brave), ko... list goes on.
What are some alternatives?
dream2nix - Simplified nix packaging for various programming language ecosystems [maintainer=@DavHau]
skopeo - Work with remote images registries - retrieving information, images, signing content
arion-compose - Run docker-compose with help from Nix/NixOS
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
nix-gaming - Gaming on Nix
container-diff - container-diff: Diff your Docker containers
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
image-spec - OCI Image Format
bob - Bob is a high-level build tool for multi-language projects.
gcr-cleaner - Delete untagged image refs in Google Container Registry or Artifact Registry
nixpkgs - Nix Packages collection & NixOS
docker-tools - This is a repo to house some common tools for our various docker repos.