They do have more details on the Docker container approach in one of the pages as well: https://switch2osm.org/serving-tiles/using-a-docker-containe...

Here's the relevant Docker Hub link: https://hub.docker.com/r/overv/openstreetmap-tile-server

The requirements are considerable, though, given the workload:

> Serving your own maps is a fairly intensive task. Depending on the size of the area you’re interested in serving and the traffic you expect the system requirements will vary. In general, requirements will range from 10-20GB of storage, 4GB of memory, and a modern dual-core processor for a city-sized region to 1TB of fast storage, 24GB of memory, and a quad-core processor for the entire planet.

Personally, for lower end mobile devices raster tiles still seem to perform better, when compared with at least some of the current vector tile implementations. I actually recorded a short comparison on my phone a while back: https://www.youtube.com/watch?v=A-IRtBGO9rM