pacoloco
distroless
pacoloco | distroless | |
---|---|---|
9 | 122 | |
191 | 17,781 | |
- | 1.2% | |
7.1 | 9.4 | |
6 days ago | 1 day ago | |
Go | Starlark | |
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.
pacoloco
-
Default Pacoloco config
Then there's no man page, and the info available on https://github.com/anatol/pacoloco was confusing to me as well. I think there may be a language interpenetration related barrier at play here.
-
Can i maintain arch with a limited data plan ?
If you have multiple systems, take a look at pacoloco. It won't save you from having to download the updates once, but after you update one computer, the others sharing the same packages can download from the cache. If you have numerous machines running arch, this will save you a LOT of bandwidth.
-
pacoloco urls vs mirrorlist
Hello, I've just been trying to get pacoloco installed and running on my network, and I seem to have it working with more or less the defaults, but i'm confused about one thing.
-
Why do i need to re-download base package when the ISO installer have it already?
The much simpler solution is if you want to save bandwidth, for example if you are installing Arch on a bunch of machines is to either create your own Arch install on removable media (https://wiki.archlinux.org/title/Install_Arch_Linux_on_a_removable_medium) with a local repository with the packages you want (https://wiki.archlinux.org/title/pacman/Tips_and_tricks) or a networked shared pacman cache. I like pacoloco (https://github.com/anatol/pacoloco), but there are others.
-
are Stable/static distros better for slower internet speeds?
Pacoloco https://github.com/anatol/pacoloco might be useful for you
-
The best way to build docker images in go 1.17
Pacoloco project uses simple and nice way to build images from scratch. See it here https://github.com/anatol/pacoloco/blob/master/Dockerfile
-
Paralelle Donwloads for Pacman
Try https://github.com/anatol/pacoloco pacman cache server and see if you still have these errors. I pretty much sure pacoloco works at RPi.
-
When will pacman with parallel download capability go 'stable' in the main repo?
Parallel download would especially help people who have multiple repos with different speed. e.g. some part of packages is cached locally with pacoloco while other packages need to be fetched via slow high-latency connection.
distroless
-
Chainguard Images now available on Docker Hub
lots of questions here regarding what this product is. I guess i can provide some information for the context, from a perspective of an outside contributor.
Chainguard Images is a set of hardened container images.
They were built by the original team that brought you Google's Distroless (https://github.com/GoogleContainerTools/distroless)
However, there were few problems with Distroless:
1. distroless were based on Debian - which in turn, limited to Debian's release cadence for fixing CVE.
2. distroless is using bazelbuild, which is not exactly easy to contrib, customize, etc...
3. distroless images are hard to extend.
Chainguard built a new "undistro" OS for container workload, named Wolfi, using their OSS projects like melange (for packaging pkgs) and apko (for building images).
The idea is (from my understanding) is that
1. You don't have to rely on upstream to cut a release. Chainguard will be doing that, with lots of automation & guardrails in placed. This allow them to fix vulnerabilties extremely fast.
- Language focused Docker images, minus the operating system
-
Using Alpine can make Python Docker builds 50Γ slower
> If you have one image based on Ubuntu in your stack, you may as well base them all on Ubuntu, because you only need to download (and store!) the common base image once
This is only true if your infrastructure is static. If your infrastructure is highly elastic, image size has an impact on your time to scale up.
Of course, there are better choices than Alpine to optimize image size. Distroless (https://github.com/GoogleContainerTools/distroless) is a good example.
- Smaller and Safer Clojure Containers: Minimizing the Software Bill of Materials
-
Long Term Ownership of an Event-Driven System
The same as our code dependencies, container updates can include security patches and bug fixes and improvements. However, they can also include breaking changes and it is crucial you test them thoroughly before putting them into production. Wherever possible, I recommend using the distroless base image which will drastically reduce both your image size, your risk vector, and therefore your maintenance version going forward.
-
Minimizing Nuxt 3 Docker Images
# Use a large Node.js base image to build the application and name it "build" FROM node:18-alpine as build WORKDIR /app # Copy the package.json and package-lock.json files into the working directory before copying the rest of the files # This will cache the dependencies and speed up subsequent builds if the dependencies don't change COPY package*.json /app # You might want to use yarn or pnpm instead RUN npm install COPY . /app RUN npm run build # Instead of using a node:18-alpine image, we are using a distroless image. These are provided by google: https://github.com/GoogleContainerTools/distroless FROM gcr.io/distroless/nodejs:18 as prod WORKDIR /app # Copy the built application from the "build" image into the "prod" image COPY --from=build /app/.output /app/.output # Since this image only contains node.js, we do not need to specify the node command and simply pass the path to the index.mjs file! CMD ["/app/.output/server/index.mjs"]
-
Build Your Own Docker with Linux Namespaces, Cgroups, and Chroot
Lots of examples without the entire OS as other comments mention, an example would be Googles distroless[0]
[0]: https://github.com/GoogleContainerTools/distroless
-
Reddit temporarily ban subreddit and user advertising rival self-hosted platform (Lemmy)
Docker doesn't do this all the time. Distroless Docker containers are relatively common. https://github.com/GoogleContainerTools/distroless
-
Why elixir over Golang
Deployment: https://github.com/GoogleContainerTools/distroless
-
Reviews
Or use distroless image as it includes one, among others. https://github.com/GoogleContainerTools/distroless/blob/main/base/README.md
What are some alternatives?
prep4ud - Speed up Arch Linux system updates via pre-downloading packages
iron-alpine - Hardened alpine linux baseimage for Docker.
changelog - A changelog generator which uses GitHub's API for the details
spring-boot-jib - This project is about Containerizing a Spring Boot Application With Jib
pack - CLI for building apps using Cloud Native Buildpacks
jib - π Build container images for your Java applications.
podman - Podman: A tool for managing OCI containers and pods.
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
docker-alpine - Official Alpine Linux Docker image. Win at minimalism!
whalebrew - Homebrew, but with Docker images
example-bazel-monorepo - πΏπ Example Bazel-ified monorepo, supporting Golang, Java, Python, Scala, and Typescript
fpm - Effing package management! Build packages for multiple platforms (deb, rpm, etc) with great ease and sanity.