[arjie]

For the most part people decide to create Docker containers like they're deploying everything to heavy prod so they chop the image down super narrow. Just solve for your own use-case. I run my blog and other things on a homeserver with a Cloudflare reverse proxy in front of it and I don't use `docker` strictly but I do use systemd quadlets and podman and it's the same thing.

If you're upset with your tooling in your Docker image, just make it so you can become root in it, make sure it has debug tooling, and so on and so forth. Nothing stops you from running `updatedb` and `locate` in it. It's just an overlayfs for the fs nothing fancy.

I understand somewhat the urge for this. There is some containerization overhead and at a small prop trading shop we wouldn't do it (apart from the annoyance of plumbing onload etc. I never figured out how to control scheduling properly) but for most things containers are a godsend.

[udev4096]

I am not entirely sure but afaik overlayfs is only if you use docker volumes and not bind mounts