Unfortunately there’s no way to have a generated TOC within the page itself. It’s usually in a sidebar or something like that.

sqlboiler does this in Go

I think one of the issues I had was trying to run pihole with podman on a raspberry pi. I could not get DNS requests to work by just mapping the right ports. I ended up just running with --net=host and it worked, I didn’t feel like debugging further.

I had other issues on my NAS but I don’t remember what it was, I have a lot of services on it, qBittorrent, Wireguard, Jellyfin, Jackett, netdata, prometheus, samba, syncthing, pihole (redundant), wsdd all in docker.

I tried replacing some components of my NAS server that were on docker/docker-compose with podman but unfortunately it was not a 100% drop-in replacement. I had networking issues in podman that I did not have in docker.

The network stack is implemented quite differently in podman than in docker, once you start using more advanced features the backward compatibility disappears.

Since it came second, I think it has a lot of technical advantages, avoiding docker’s mistakes and what not. In the long term I’ll probably switch to it, unless Redhat keeps shooting itself in the foot…

Ahh okay je vois. Je cherchais “poo” sur google, les résultats étaient pas génials.

That’s pretty decent. I’m not convinced about the 16 core limit though, the 12700H has 6 P-cores, 8 E-cores and 6 threads, totalling “20 cores”. Not the best chip to benchmark multicore workloads

what is POO? Can’t find a definition on google

Is there a place that has a list of classic programming articles like this? Such a fun read. I know PHK has another one of the design of Varnish vs Squid here https://varnish-cache.org/docs/trunk/phk/notes.html

I used to use LXC maybe 5 years ago but I’ve since replaced everything with docker/compose. The main difference between LXC and Docker is that LXC is meant to be more like a Virtual Machine than a container. LXC containers run their own instance of systemd and can run multiple processes easily. Docker is meant to run a single process although people sometimes do hacks with supervisord or s6 overlay to run multiple processes.

At the time LXC didn’t really have a concept of images like Docker, it was just base images like Ubuntu 18.04 or Debian 9 and you’d shell in the container and install your stuff.

LXD is a tool built on top of LXC, confusingly enough the LXD client is called lxc… It’s higher level and might have the ability to use images, not sure, I never felt the need to learn it.