doks-debug
nixery
| doks-debug | nixery | |
|---|---|---|
| 1 | 18 | |
| 149 | 1,862 | |
| 6.0% | 1.1% | |
| 6.3 | 3.4 | |
| 7 months ago | about 2 months ago | |
| Dockerfile | 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.
doks-debug
nixery
- Way to get NVM working in CI/CD systems
-
What's your favourite Docker Image, and why?
The ones from https://nixery.dev/
-
k8s docker image with basic troubleshooting tools
You can build your own with https://nixery.dev/
-
Crafting container images without Dockerfiles
I built a service for doing this ad-hoc via image names a few years ago and it enjoys some popularity with CI & debugging use-cases: https://nixery.dev/
-
Nixpacks takes a source directory and produces an OCI compliant image
name is eerily similar to `nixpkgs`, i.e. the monorepo that defines all packages and one of the underlying technologies here. i get the play on buildpacks, but still, as a nix user it makes me do a double take reading the name
this is neat though, and in political terms, the elevator pitch mentions nix itself as an implementation detail in passing. hopefully, if this catches on, it'll function as a non-threatening gateway drug to nix itself, when users inevitably go digging into the weeds
for anyone interested, prior art on the nix container front: https://nixery.dev
-
Ask HN: Have You Left Kubernetes?
Wow, this is excellent! At a previous job, we had been using k8s + knative to spin up containers on demand, and likewise were unhappy with the delays. Spawner seems excellent.
One question: have you had to do any custom container builds on demand, and if so, have you had to deal with large containers (e.g. a Python base image with a few larger packages installed from PyPI)? We would run up against extremely long build image times using tools like kaniko, and caching would typically have only a limited benefit.
I was experimenting using Nix to maybe solve some of these problems, but never got far enough to run a speed test, and then left the job before finishing. But it seems to me some sort of algorithm like Nixery uses (https://nixery.dev) to generate cacheable layers with completely repeatable builds and nothing extraneous would help.
Maybe that's not a problem you had to solve, but if it is, I'd love your thoughts.
-
Hacker News top posts: Apr 19, 2022
Nixery – Docker images on the fly with Nix\ (38 comments)
- Nixery – Docker images on the fly with Nix
What are some alternatives?
koolkits - 🧰 Opinionated, language-specific, batteries-included debug container images for Kubernetes.
BirdNET-Pi - A realtime acoustic bird classification system for the Raspberry Pi 4B, 3B+, and 0W2 built on the TFLite version of BirdNET.
netshoot - a Docker + Kubernetes network trouble-shooting swiss-army container
keppel - Regionally federated multi-tenant container image registry
alnoda-workspaces - :fireworks: Flexible and extendable containerized workspaces. Now. with free offline chat GPT!!! 🚀🚀🚀
template-nix - The nix template, configured for Gitpod (www.gitpod.io) to give you pre-built, nix based ephemeral development environments in the cloud.