#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

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

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

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

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

@pak21 It seems to be yet another #bitnami fuckover :(
```
ErrImagePull: rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/os-shell:12-debian-12-r15": failed to resolve reference "docker.io/bitnami/os-shell:12-debian-12-r15": docker.io/bitnami/os-shell:12-debian-12-r15: not found
```

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

As former #bitnami #keycloak user we now managed to move away:

https://domaindrivenarchitecture.org/

#DevOps #c4k #clojure #k8s

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.

Finally completed a replacement of the Bitnami charts and images we had in a project.
It's no secret that when you do such a thing, you invest way more effort than if you'd need with using their new free versions.
But! They broke a trust to a software provider, they undid literally years spent on delivering all these artifacts.
So, any sane person would rather jump off their shit train, which I did as well.

#Kubernetes #k8s #DevOps #Bitnami

https://github.com/bitnami/charts/issues/35164 - #Bitnami was bought by #Broadcom and is now going closed-source. #images on #Docker Hub are moving to "legacy" and getting abandoned. Or start paying. https://thenewstack.io/broadcom-ends-free-bitnami-images-forcing-users-to-find-alternatives/

Bitnami is updating some of the their kubernetes helm charts and moving this to a legacy repo

https://piefed.keyboardvagabond.com/c/selfhost/p/148400/bitnami-is-updating-some-of-the-their-kubernetes-helm-charts-and-moving-t

#Bitnami/#Broadcom just freaking... deleted all of their old/free #Docker images - and now my #PostgreSQL/#MariaDB/#MySQL deployments have just lost the ability to re-pull their images, which I don't have stored locally anywhere atm. What the actual.. fuck, Broadcom?

---

edit: hope?

🔗 https://hub.docker.com/u/bitnamilegacy

#docker #Bitnami ist für mich endgültig gestorben.

Erst verlieren neuere #PHP Versionen #XDebug, und jetzt für #Postgres, #Apache , ....

bitnami/apache:latest not found: manifest unknown: manifest unknown

F*uck you, so geht's nicht. Wieder sinnlose arbeit für mich.

#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

#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

#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

#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

#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

https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/
#Drubernetes #Kubernetes #Drupal #Terraform #MariaDB #Bitnami #OpenSource #IaC #Helm #CloudComputing #Licensing

https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/
#Drubernetes #Kubernetes #Drupal #Terraform #MariaDB #Bitnami #OpenSource #IaC #Helm #CloudComputing #Licensing

https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/
#Drubernetes #Kubernetes #Drupal #Terraform #MariaDB #Bitnami #OpenSource #IaC #Helm #CloudComputing #Licensing

https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/
#Drubernetes #Kubernetes #Drupal #Terraform #MariaDB #Bitnami #OpenSource #IaC #Helm #CloudComputing #Licensing

Oublié de corriger les #helm chart de #Mastodon après le coup de poignard dans le dos de #Bitnami... Base PostgreSQL en l'air. Corrigé avec les images "legacy" mais il va falloir que je fasse en sorte de sortir de l'impasse qu'ils nous ont imposée.
Moralité, je finirai de faire mon repo avec mes propres helm chart pour les services importants (maria en mode Galera / Monoservice, Postgres, FerretDB pour remplacer Mongo...) et bye bye les enfoirés qui ont pourri le libre et l'open source.

On the topic of #Bitnami choosing to block free access to their container builds of open source software: there's a lesson there. Something about putting all your eggs in someone's else's basket or something like that. Also, taking free things for granted. I know you can get around it, but it's a temporary workaround and not a solution, nor a Plan B.

Ah, heute scheint der Tag zu sein, an dem ich rausfinde, wo ich überall noch #bitnami Container Images laufen habe.

#ImagePullBackOff

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

I use one #bitnami thing. One. I somehow missed their announcement from the end of August that they were mothballing all of their open source stacks. What the actual fuck? Their open source stuff had 4 BILLION downloads in the 12 months leading up to the end of August.

https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/

Ecco un ripologo interessante sugli effetti sul mondo dello sviluppo software (proprietario e libero) dell'acquisizione di alcune grosse aziende informatiche negli ultimi anni. #broadcom #vmware #bitnami #HockTan
https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/

There are currently too many supply chain issues... #bitnami #npm #ruby
All of them on different levels #ActuallyNotAmused

https://blog.gslin.org/archives/2025/09/01/12605/bitnami-%e8%b5%b0%e5%90%91%e8%a8%82%e9%96%b1%e5%88%b6/

Bitnami 走向訂閱制

#bitnami #container #cost #docker #image #registry #security #subscription #vmware

I feel like everyone has been talking about Bitnami putting there images behind paywalls lately, especially with Redis

Then I'm here like, what if I was finally putting the nail in the coffin for Redis and move to the Valkey operator <_<

#selfhosted #homelab #valkey #redis #bitnami #migration #paywall #enshitification

“A massive pile of debt from the VMware acquisition is forcing Broadcom to squeeze every penny from assets we once considered sacred.” read here

#broadcom #docker #bitnami

we really need sovereign public registries like public services https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time

Luckily, I am so devoted to the idea of control of all my data, and giving my clients full control of their data, to a degree that reveals my autism (much to the annoyance of perhaps a few folks), this news that Bitnami is shifting everything to a paid account absolutely doesn't affect me or my clients.

https://linuxiac.com/bitnami-ends-free-stable-images-users-forced-to-migrate-or-pay/

#Bitnami #Enshittification

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

Number of #bitnami container images in the #homelab cluster: 4

Number of #bitnami container images successfully removed: 2

Number of #bitnami container images to remove: 1

Next up was redis. Harbor doesn't support a full redis cluster so I searched around for a primary-secondary configuration. Looks like the DandyDeveloper helm chart should do the business so we are off to the races... Two down, one to go!

https://github.com/DandyDeveloper/charts/tree/master/charts/redis-ha

#homelab #kubernetes #docker #mariadb #galera #redis

Number of #bitnami container images in the #homelab cluster: 4

Number of #bitnami container images successfully removed: 1

Number of #bitnami container images to remove: 2

First up was mariadb-galera, this may end up being a blocg post as I ended up creating my own configuration. I tried the mariadb-operator but it doesn't support scaling down the cluster so it was quickly ruled out...

#homelab #kubernetes #docker #mariadb #galera

Broadcom to discontinue free Bitnami Helm charts

https://github.com/bitnami/charts/issues/35164

#HackerNews #Broadcom #Bitnami #Helm #charts #discontinuation #open #source #news #technology

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

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

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

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

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

Развертывание защищенного dev кластера bitnami/kafka в k8s с помощью helm

Всем привет. На этот раз хотел бы поделиться материалом, связанным непосредственно с devops работой. Недавно возникла потребность раскатить kafka кластер в kubernetes. В ходе развертывания возникло очень много сложностей, встречено множество подводных камней, и, естественно, в большинстве случаев рецепта в интернете найдено не было, поэтому приходилось искать решения самостоятельно методом проб и ошибок. Все, что здесь будет описано это сугубо личный опыт на одном из проектов. Сегодня я расскажу как с нуля раскатить dev контур bitnami/kafka кластера с помощью helm чартов, как обезопасить ваш кластер kafka и какие сложности могут вам встретиться.

https://habr.com/ru/articles/803969/

#kubernetes #helm #k8s #kafka #bitnami #ssl #tls #security #sasl #authentication