vmware-host-modules-builder-cli VS containers

I compared the two to understand them. The TLDR on nala is "fast apt". Topgrade finds the distro and uses the appropriate upgrade tool, plus gets things like brew, cargo, pip, snap, flatpak and fwupd. On Pop!, Topgrade will use nala instead of apt if it's installed (so that part is faster). That last part surprised me so I looked at the source code in the repo. I'm not a Rust programmer, but the code is readable and you can see the logic. You're right, topgrade is a wrapper and you could just make a shell script yourself (that's what I used to do). The benefit here is that the script is being maintained and improved. The "gotcha" with Pop! upgrades for me is VMWare Workstation. Kernel updates break vmmon and vmnet and they have to be recompiled. I recommend the VMWare host modules Builder CLI project. I wrote about it here.

Found an automated solution : https://github.com/david-kariuki/vmware-host-modules-builder-cli

This might help Link

There are multiple benefits of using the images from Bitnami. We can refer to their github repo for additional details. The Bitnami image from cassandra provides us the option to override few of the configurations in the cassandra.yaml file by passing the values as environment variables. For eg: When we provide an environment variable - CASSANDRA_CLUSTER_NAME – to the container, the value of this variable gets updated in the cassandra.yaml -> cluster_name field.

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