Skip to content
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.

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

Running 2 separate instances of gluetun with different regions #84

Closed
Dante2202 opened this issue Jun 27, 2024 · 2 comments
Closed

Running 2 separate instances of gluetun with different regions #84

Dante2202 opened this issue Jun 27, 2024 · 2 comments

Comments

@Dante2202
Copy link

URL to the Wiki page

https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/multiple-gluetun.md

What's missing?

The advanced faq states this can easily be done but there aren’t any docker compose examples of how to set up another container running gluetun if you already have one running to avoid any conflicting ports or issues.

Would anyone who has accomplished this be able to provide an example of how to set this up please?

@EliotFR44
Copy link

EliotFR44 commented Jun 28, 2024

Hi,
Are you a proxy ?
Btw, you simply run your command twice, with different container names and different configurations.
My personal record is 600 glueten on the same hardware host.

@qdm12
Copy link
Owner

qdm12 commented Jul 8, 2024

if you already have one running to avoid any conflicting ports or issues.

This is kind of obvious, you cannot publish the same ports on your host for 2 different containers.
I don't believe an example is needed, and as @EliotFR44 said

Btw, you simply run your command twice, with different container names and different configurations.

My personal record is 600 glueten on the same hardware host.

Shit me, I didn't know you could push it that far 😄

@qdm12 qdm12 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants