
Buildah
Podman
containerd
CRI-O
Crane
ZeroVM
BuildKit
LXD
pkgsrc
Conda
Homebrew
Yay
Portage
Nix
Docker
BBEdit
Buildah
pkgsrcBuildah might be a bit more popular than pkgsrc. We know about 14 links to it since March 2021 and only 11 links to pkgsrc. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Modern Docker releases use BuildKit, an efficient builder developed by Docker, whereas Podman uses Red Hat's Buildah. However, both solutions output OCI-compliant images, so there's no practical difference between the two for standard build workflows. - Source: dev.to / 12 months ago
I suspect that the GP was really asking "why not use a different tool", like buildah , buildpacks , nix ,. - Source: Hacker News / over 1 year ago
Buildah specializes in building OCI-compliant container images, offering a more granular and secure approach to image creation compared to traditional Dockerfile builds. - Source: dev.to / over 1 year ago
Lockdown your Dockerized build environments --- Because privileged mode is insecure, you should restrict your CI/CD environments to known users and projects. If this isn't feasible, then instead of using Docker, you could try using a standalone image builder like Buildah to eliminate the risk. Alternatively, configuring rootless Docker-in-Docker can mitigate some --- but not all --- of the security concerns... - Source: dev.to / about 2 years ago
In my experience, not using docker to build docker images is a good idea. E.g. buildah[0] with chroot isolation can build images in a GitLab pipeline, where docker would fail. It can still use the same Dockerfile though. If you want to get rid of your Dockerfiles anyway, nix can also build docker images[1] with all the added benefits of nix (reproducibility, efficient building and caching, automatic layering,... - Source: Hacker News / over 2 years ago
> Most open source software packages are also compiled for BSD variants, they switched to 64 bit time_t a long time ago and reported back upstream any problems. * NetBSD in 2012: https://www.netbsd.org/releases/formal-6/NetBSD-6.0.html * OpenBSD in 2014: http://www.openbsd.org/55.html For packaging, NetBSD uses their (multi-platform) Pkgsrc, which has 29,000 packages, which probably covers a large swath of... - Source: Hacker News / 12 months ago
> https://pkgsrc.smartos.org/install-on-macos/ Note that Pkgsrc is a NetBSD-derived project. * https://pkgsrc.org The Joyent folks leveraged it to allow their customers, who were perhaps not as familiar with Solaris/SmartOS, a larger pool of packages. Pkgsrc was running on Solaris before Joyent, Joyent built on top of it. - Source: Hacker News / almost 2 years ago
Https://pkgsrc.org/ from netbsd runs on many systems. - Source: Hacker News / about 2 years ago
It seems according to pkgsrc.org that pkgin might follow the PKG_PATH environment variable. You're supposed to set PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r|cut -f '1 2' -d.)/All/", and according to uname(1), -p gives the processor architecture and -r gives the operating system [kernel] release. Source: over 3 years ago
It seems like pkgsrc.org hasnโt got the news yet. Source: over 3 years ago
Podman - Simple debugging tool for pods and images
Conda - Binary package manager with support for environments.
containerd - An industry-standard container runtime with an emphasis on simplicity, robustness and portability
Homebrew - The missing package manager for macOS
CRI-O - Lightweight Container Runtime for Kubernetes
Yay - Yay is an AUR helper written in go, based on the design of yaourt, apacman and pacaur.