Run Nginx as a caching reverse proxy in its own container on the same Docker network as your WordPress container, so the whole setup stays portable and independent of the host. The same caching principles apply as when Nginx serves WordPress directly, but instead of fastcgi_pass to a local PHP socket you proxy_pass to the WordPress container’s service name over HTTP, and you must forward the Host header plus client IP headers so WordPress generates correct URLs. Exclude wp-admin, wp-login.php, and requests with logged-in cookies from the cache to avoid serving private content. Any plain WordPress image works fine as an upstream, so no special image is needed, just keep Nginx and WordPress as separate containers.
