coreweave/nginx-proxy-connect-stable-alpine

coreweave/nginx-proxy-connect-stable-alpine

Description: nginx:stable-alpine + proxy_connect (multiarch image)

Stars: 0

Forks: 0

Open issues: 0

Created: 2024-01-19T15:47:55Z

Pushed: 2025-08-07T02:54:38Z

Default branch: master

Fork: yes

Parent repository: rpardini/nginx-proxy-connect-stable-alpine

Archived: no

README:

nginx:stable-alpine + proxy_connect

Upstreams:

• nginx:stable-alpine (due this has since long diverged)
• ngx_http_proxy_connect_module

I removed gpg sig verification for the sake of faster builds. Also most modules with external dependencies were removed.

master (:latest) is actually unstable

For stable versions, use the tagged builds, eg, nginx-1.18.0-alpine-3.12.1

Usage

It's on Docker Hub; :latest is from master and unstable.

docker run -it -p 8081:80 rpardini/nginx-proxy-connect-stable-alpine

• Just like nginx:stable-alpine, but you can use proxy_connect;.
• Also proxy_connect_address $someVar; is supported; this has the "rewrite" version of the patch
• you can map on $connect_host
• log $connect_addr for host:port of the final destination

Why?

I wanted a more contained way of doing DNS overrides.

If you can convince a client program to use an https proxy, and inject your own CA certificate as trusted, you can use proxy_connect to send traffic to a second nginx server and do caching, filtering, rewriting, and who knows what else there.