#bitnami — Public Fediverse posts

One of my fears of homelabbing is the reliance on (3rd party) #Docker/#container images that could just be gone someday. I've already had it happen once, with #Bitnami images (fuck #Broadcom).

One way I previously thought to combat this is to manually pull the image bundle and host it in your own container registry. This works, but obviously not a reasonable effort to do and reproduce for more than ~1-2 images.

Then, the moment I discovered #Amazon/#AWS has such a thing that addresses this - pull through cache for their #ECR, I looked up on how I can have the same kind of setup on my #homelab, and sure enough, there are already several options. I went with #Zot, and it's working pretty freaking well. Now, anytime I pull any images from registries I've configured Zot to sync like #GitHub's ghcr.io, docker.io, public.ecr.aws, they'll all be pulled/cached first on my own Zot instance and stored for good there.

Man, I wish I looked into this much earlier - but better late than never.

🔗 https://github.com/project-zot/zot

🔗 https://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-through-cache-creating-rule.html

WEW #MASTODON ON CLOUDNATIVE-PG! FINALLY OFF #BITNAMI at least for #postgres. #cnpg

Fuck #bitnami btw, they are made it infinitely harder by their change about the helm charts and docker images and what not. #boos #angry

Fuck #bitnami btw, they are made it infinitely harder by their change about the helm charts and docker images and what not. #boos #angry

Fuck #bitnami btw, they are made it infinitely harder by their change about the helm charts and docker images and what not. #boos #angry

Fuck #bitnami btw, they are made it infinitely harder by their change about the helm charts and docker images and what not. #boos #angry

Fuck #bitnami btw, they are made it infinitely harder by their change about the helm charts and docker images and what not. #boos #angry

The #MSTDNDK Mastodon instance just migrated away from Bitnami's #Redis helm chart and container images to #Valkey.

#Bitnami and Redis both seem to be exiting the open source community, which could prevent us from staying current, meaning always running the latest versions of the software components that make up this instance.

We understand the need to monetize software, but see that as an opportunity to add premium paid features, not take away existing ones from open source. Doing so will make your potential future customers look for other solutions. Looking at you, #MinIO, Redis and Bitnami.

Please report any issues you might experience as a result of the move to Valkey. So far it looks peachy.

#Distroless #OCI containers to replace #Bitnami images. Governments explore different options: #Nix_Flakes custom builds, community images.

Read my take and another option based on #Fedora at https://blog.riemann.cc/digitalisation/2025/10/26/distroless-containers-nix-flakes-vs-fedora/

What is your view?

#opensuse #podman #NixOS #digitialsovereignty #supplychain #NIS2

Headsup - Bitnami have just removed a load of docker tags/images from Docker Hub. If you use any Bitnami images it's worth checking that you're still going to be able to start new containers and update image references.

We'd built a system using Redis, and it's now broken because of this.

We'd normally push third-party images to our own registry but it looks like someone forgot to do that in this case (that someone being me). Don't be like me.

#docker #tech #redis #bitnami #kubernetes #aws #gke #cloud

The Deletion of Docker.io/Bitnami

https://community.broadcom.com/tanzu/blogs/beltran-rueda-borrego/2025/08/18/how-to-prepare-for-the-bitnami-changes-coming-soon

#HackerNews #Docker #Deletion #Bitnami #Changes #TechNews #Community

There are several security vulnerabilities in #XAMPP (#Apache #ApacheHTTPd #PHP #Perl #MySQL #MariaDB #OpenSSL #phpMyAdmin #Curl #Tomcat #libexpat), I have done the official announcement, please share! (#ApacheFriends #Bitrock #Bitnami #VMware #Broadcom) https://github.com/Neustradamus/xampp

If you are stuck dealing with #CrunchyData or #Bitnami for modern #postgresql in #k8s, let me turn you on to cloudnative-pg.io

TL;DR: An operator and CRDs for managing #psql on #k8s that actually fulfills the promise of the operator pattern. It just, you know, *operates* the stupid thing for you. And its multi-arch.

Amusingly, I found out about it because Crunchydata insists that ARM is super hard and reserved for enterprise customers only. (They've since made contrite noises about walking that back, but no actual movement yet.)

I've been running it for about 15 minutes and so far I am blown away. And weirdly it does not appear to have tried to spy on me! That oversight aside, it comes with full #prometheus support, base alarms, and a VERY nice #grafana dashboard. Handles clustering, failover, scaling, upgrades, all the things.

#postgresql #cloudnative #kubernetes #arm64 #homelab #turingpi

If you're using #contour on #kubernetes with the #bitnami helm charts you probably want to check this PR. It saved hundreds of gigabytes RAM in our cluster. Memory requests value for contour deployment got applied to envoy daemonset... https://github.com/bitnami/charts/pull/18366