New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Expose SOCK5 Proxy #6

Open

sfc9982 opened this issue Oct 29, 2022 · 1 comment

sfc9982 commented Oct 29, 2022

Could you let the docker expose a SOCKS5 proxy?
I've tried to modify your code, but failed.
Thanks.

Owner

aw1cks commented Oct 31, 2022 •

edited

Loading

Hi there,

I'd recommend using something like docker-compose to put a proxy from another container in front of this one.

For example, you can do something like this:

---

openconnect:
  image: aw1cks/openconnect:latest
 <configure openconnect container here>

...

socks:
  # Using Squid as an example here,
  # any SOCKS-compatible proxy works fine
  # N.B. you probably need to configure Squid to do SOCKS - by default it will only do HTTP proxy
  image: ubuntu/squid:latest
  ports:
    - "3128:3128"
  restart: always
  # This will route the proxy's traffic through the `openconnect` service defined above
  network_mode: service:openconnect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment