that’ll teach me to type in a hurry. I meant df, not du. Lookup man page for options

I’d be curious to see du -i to see what’s going on with inodes. Alternatively I did have an issue long time ago with docker containers, sparse files and dirty disk. Force-running fsck resolved my issues in the past.

Incorrect. In certain areas (like mine) only grass grows very well and is very prolific chocking off any other species. Grazers make a lot more sense and a lot less impact. Including soil build-up for future crop raising.

this only holds for industrial red meat. I love it when everything gets lumped together and presented as “evidence”. Non-industrial, small scale farming actually can have reverse effect. But we don’t talk about avoiding industrial products, because… why? 100mile diet that includes sustainably raised meat (white, red blue - whatever) from local farm will have minimal impact on environment. Shall we talk about avocados in Canada or Almonds? Study lacks nuance and produces flashy headings with no substance.

My opinion is that of the two Postres is more “adult”. So if you want to"just wing it" MariaDB would work, but if you’re serious Postgres is a better choice. However Postgres also requires better understanding of you setup etc. So it’s a ROI game - what’s more important to your project, how complex your DB is, what are the requirements for availability, transaction security etc. There is no “better” or “worse” there’s “feasible” and “prohibitive” 😉

I’m not convinced what you run into is a specific podman issue. It’s a resource issue and configuration issue likely. “vanila” podman with proper rootless containers will run as much workload as machine can handle from my experience. My company costomers seem to be running production workloads with it just fine.

Oh wait, by rootless container you really meant running podman rootless? still don’t see an issue though. What specifically are you doing? I mean, what’s the configuration and what’s the workload?

Removed by mod

thank you for such a detailed response. I would love to contribute however at the moment my capacities are rather limited but otherwise I’d be willing to add sqlite adapter. From your description it sounds like currently architecture is narrowly locked on PostgreSQL features. In my daily job I love PostgreSQL for big apps and stacks but I’m also aware how “hungry” PG can be, which is why I’m wondering whether it’s “too big of a hammer” for this particular problem. Also, setting up single service is easier to novices vs maintaining several. Docker compose is nice but it has it’s limitations.

@mgdigital, first thing I’be noticed: reliance on “heavier” database stack (pg + redis), at least from the first glance at docker-compose. My suggestion would be to have an option for minimalist setup with sqlite and without redis if possible. That would work better for those of us flying with minimal hardware (rpi, old PC and such).