distroless
fpm
distroless | fpm | |
---|---|---|
126 | 38 | |
19,806 | 11,220 | |
1.6% | 0.3% | |
9.1 | 6.8 | |
4 days ago | about 2 months ago | |
Starlark | Ruby | |
Apache License 2.0 | MIT-like |
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.
distroless
-
Revisit base container image for AWS services
Debian slim and UBI are easy to use in the direction of creating a very small image while taking into account the use of a package manager, but on the other hand, they are too large to satisfy the demand to create a minimum image for a specific language environment. If you want to satisfy such a demand, Distroless image may be the right choice for you.
-
Base Images: The Secret to Smaller Docker Images
As Google, the creator of distroless images, puts it, "Distroless images contain only your application and its runtime dependencies." You can read more about them here.
- Distroless: Language focused Docker images, minus the operating system
-
Docker, Linux, Security. Kinda.
That's how we get distroless. Distroless base images follow the same pattern as alpine base docker images, as in, less functionality while still keeping enough functionality to be able to do the job and minimize the attack surface. Minimizing a base image like this means that the base images are very specialized so we have base images for golang, python, java and the like.
-
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"]
fpm
-
Debian Discusses Vendoring yet Again
If you ever revisit that decision, check out FPM. It can shave off a few of the rough edges related to packaging: https://github.com/jordansissel/fpm
- Fpm – Packaging Made Simple
- PackagingCon – a conference only for software package management
- Makefile to .deb
-
Been adding a little more polish to my Battle Network/ Smash bros inspired game.
The easiest way is probably FPM: https://fpm.readthedocs.io/en/latest/
-
Zrok: open-source peer to peer sharing with ability to selfhost
There is definitely a lot more to building a proper package for wider distribution, but there are some great tools out there for folks wanting to get into it that make it more approachable. I've done my fair share with fpm when learning how the proverbial sausage is made.
-
Can i create deb file from source code?
Check out https://github.com/jordansissel/fpm
- List of Apps I need that are not in repo or flathub
- Can someone point me in the right direction for automating RPM builds?
-
What's the deal with Slackware?
I use RedHat based environments for work. I've had good success creating my own yum repo and building RPM packages with Effing package management. FPM can handle packages for most distros so if you want to publish a linux app it is an easy way to provide it in multiple formats.
What are some alternatives?
iron-alpine - Hardened alpine linux baseimage for Docker.
Linuxbrew
jib - 🏗 Build container images for your Java applications.
Homebrew-cask - 🍻 A CLI workflow for the administration of macOS applications distributed as binaries
docker-alpine - Official Alpine Linux Docker image. Win at minimalism!
CocoaPods - The Cocoa Dependency Manager.
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
Homebrew
dive - A tool for exploring each layer in a docker image
tito - A tool for managing rpm based git projects.
spring-boot-jib - This project is about Containerizing a Spring Boot Application With Jib
omnibus-ruby - Easily create full-stack installers for your project across a variety of platforms.