containers VS distroless

Have a look at the postgresql readme file to see the value they add: https://github.com/bitnami/containers/tree/main/bitnami/post...

When you use a bunch of different containers from Bitnami, you'll start to notice common configuration patterns which make managing the containers easier.

On the flipside, the additional configuration sometimes contradicts to the official documentation, so that can add complexity from time to time.

https://github.com/bitnami/containers https://bitnami.com/stack/mariadb/containers

git clone https://github.com/bitnami/containers.git cd bitnami/APP/VERSION/OPERATING-SYSTEM

mongodb 15:53:35.21 INFO ==> ** Starting MongoDB ** mongodb 15:54:35.83 mongodb 15:54:35.83 Welcome to the Bitnami mongodb container mongodb 15:54:35.83 Subscribe to project updates by watching https://github.com/bitnami/containers mongodb 15:54:35.83 Submit issues and feature requests at https://github.com/bitnami/containers/issues mongodb 15:54:35.83 mongodb 15:54:35.83 INFO ==> ** Starting MongoDB setup ** mongodb 15:54:35.85 INFO ==> Validating settings in MONGODB_* env vars... mongodb 15:54:36.08 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment. mongodb 15:54:36.09 INFO ==> Initializing MongoDB... mongodb 15:54:36.13 INFO ==> Deploying MongoDB with persisted data... mongodb 15:54:36.15 INFO ==> ** MongoDB setup finished! ** mongodb 15:54:36.16 INFO ==> ** Starting MongoDB **

Is the chart pulling in the default bitnami/wordpress container?

I can't comment on ARM because all of my workloads are x86, but the Bitnami containers are almost always a good bet: https://bitnami.com/stacks/containers

Currently I build all of my language runtime containers myself (such as Java, Python, .NET, Node and so on) for the sake of simplicity and common tools, but when I'm dealing with something more complex to configure or turnkey software (think along the lines of Keycloak, MinIO, RabbitMQ, Redis, as well as databases like MariaDB or PostgreSQL), then I often just go with what Bitnami is offering. Here's their GitHub with a bit more information about why someone might use their images: https://github.com/bitnami/containers

Of course, do have a look at their instructions, because in the case of some of their images there can be some differences from the alternatives, for example: https://blog.kronis.dev/everything%20is%20broken/bitnami-mar... (in short, the official MariaDB image uses "/var/lib/mysql" and Bitnami MariaDB image uses "/bitnami/mariadb" for persistence; that tripped me up)

this is nice but it's not the one https://github.com/bitnami/containers/tree/main/bitnami but need to look at them more, thanks

2022-11-22 04:12:44.711598+00:00[38;5;6mpostgresql [38;5;5m04:12:44.71 [0m 2022-11-22 04:12:44.712690+00:00[38;5;6mpostgresql [38;5;5m04:12:44.71 [0m[1mWelcome to the Bitnami postgresql container[0m 2022-11-22 04:12:44.713842+00:00[38;5;6mpostgresql [38;5;5m04:12:44.71 [0mSubscribe to project updates by watching [1mhttps://github.com/bitnami/containers[0m 2022-11-22 04:12:44.714941+00:00[38;5;6mpostgresql [38;5;5m04:12:44.71 [0mSubmit issues and feature requests at [1mhttps://github.com/bitnami/containers/issues[0m 2022-11-22 04:12:44.716068+00:00[38;5;6mpostgresql [38;5;5m04:12:44.71 [0m 2022-11-22 04:12:44.727668+00:00[38;5;6mpostgresql [38;5;5m04:12:44.72 [0m[38;5;2mINFO [0m ==> ** Starting PostgreSQL setup ** 2022-11-22 04:12:44.745925+00:00[38;5;6mpostgresql [38;5;5m04:12:44.74 [0m[38;5;2mINFO [0m ==> Validating settings in POSTGRESQL_* env vars.. 2022-11-22 04:12:44.751351+00:00[38;5;6mpostgresql [38;5;5m04:12:44.75 [0m[38;5;2mINFO [0m ==> Loading custom pre-init scripts... 2022-11-22 04:12:44.754981+00:00[38;5;6mpostgresql [38;5;5m04:12:44.75 [0m[38;5;2mINFO [0m ==> Initializing PostgreSQL database... 2022-11-22 04:12:44.768199+00:00[38;5;6mpostgresql [38;5;5m04:12:44.76 [0m[38;5;2mINFO [0m ==> pg_hba.conf file not detected. Generating it... 2022-11-22 04:12:44.769498+00:00[38;5;6mpostgresql [38;5;5m04:12:44.76 [0m[38;5;2mINFO [0m ==> Generating local authentication configuration 2022-11-22 04:12:46.274760+00:00[38;5;6mpostgresql [38;5;5m04:12:46.27 [0m[38;5;2mINFO [0m ==> Starting PostgreSQL in background... 2022-11-22 04:12:49.386212+00:00[38;5;6mpostgresql [38;5;5m04:12:49.38 [0m[38;5;2mINFO [0m ==> Changing password of postgres 2022-11-22 04:12:49.416092+00:00[38;5;6mpostgresql [38;5;5m04:12:49.41 [0m[38;5;2mINFO [0m ==> Creating user mealie 2022-11-22 04:12:49.456732+00:00[38;5;6mpostgresql [38;5;5m04:12:49.45 [0m[38;5;2mINFO [0m ==> Granting access to "mealie" to the database "mealie" 2022-11-22 04:12:49.492957+00:00[38;5;6mpostgresql [38;5;5m04:12:49.49 [0m[38;5;2mINFO [0m ==> Setting ownership for the 'public' schema database "mealie" to "mealie" 2022-11-22 04:12:49.532967+00:00[38;5;6mpostgresql [38;5;5m04:12:49.53 [0m[38;5;2mINFO [0m ==> Configuring replication parameters 2022-11-22 04:12:49.563940+00:00[38;5;6mpostgresql [38;5;5m04:12:49.56 [0m[38;5;2mINFO [0m ==> Configuring synchronous_replication 2022-11-22 04:12:49.565779+00:00[38;5;6mpostgresql [38;5;5m04:12:49.56 [0m[38;5;2mINFO [0m ==> Configuring fsync 2022-11-22 04:12:49.590981+00:00[38;5;6mpostgresql [38;5;5m04:12:49.59 [0m[38;5;2mINFO [0m ==> Loading custom scripts... 2022-11-22 04:12:49.594959+00:00[38;5;6mpostgresql [38;5;5m04:12:49.59 [0m[38;5;2mINFO [0m ==> Enabling remote connections 2022-11-22 04:12:49.603284+00:00[38;5;6mpostgresql [38;5;5m04:12:49.60 [0m[38;5;2mINFO [0m ==> Stopping PostgreSQL... 2022-11-22 04:12:49.807283+00:00waiting for server to shut down.... done 2022-11-22 04:12:49.807326+00:00server stopped 2022-11-22 04:12:49.812829+00:002022-11-22T04:12:49.812829113Z 2022-11-22 04:12:49.812829+00:00[38;5;6mpostgresql [38;5;5m04:12:49.81 [0m[38;5;2mINFO [0m ==> ** PostgreSQL setup finished! ** 2022-11-22 04:12:49.837505+00:00[38;5;6mpostgresql [38;5;5m04:12:49.83 [0m[38;5;2mINFO [0m ==> ** Starting PostgreSQL ** 2022-11-22 04:12:49.858410+00:002022-11-22 04:12:49.858 GMT [1] LOG: pgaudit extension initialized 2022-11-22 04:12:49.870341+00:002022-11-22 04:12:49.870 GMT [1] LOG: starting PostgreSQL 14.5 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2022-11-22 04:12:49.870771+00:002022-11-22 04:12:49.870 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2022-11-22 04:12:49.870800+00:002022-11-22 04:12:49.870 GMT [1] LOG: listening on IPv6 address "::", port 5432 2022-11-22 04:12:49.891046+00:002022-11-22 04:12:49.890 GMT [1] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2022-11-22 04:12:49.908709+00:002022-11-22 04:12:49.908 GMT [147] LOG: database system was shut down at 2022-11-22 04:12:49 GMT 2022-11-22 04:12:49.934954+00:002022-11-22 04:12:49.934 GMT [1] LOG: database system is ready to accept connections

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.

> 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.

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.

# 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"]

Lots of examples without the entire OS as other comments mention, an example would be Googles distroless[0]

[0]: https://github.com/GoogleContainerTools/distroless

Docker doesn't do this all the time. Distroless Docker containers are relatively common. https://github.com/GoogleContainerTools/distroless

Deployment: https://github.com/GoogleContainerTools/distroless

Or use distroless image as it includes one, among others. https://github.com/GoogleContainerTools/distroless/blob/main/base/README.md