Selfhosted

40330 readers

426 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

[docker compose help] Is it possible to map ports when using network_mode? (lemmy.kde.social)

submitted 4 days ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

Hello everybody! I have the following issue: I have two countainers, let's call them C1 and C2, and they both expose the same port, let's say 1234. I want to route both of them through a gluetun container. to do this, I added

network_mode: container:gluetun

at each container. But they both expose the same port, so there's a conflict. Without routing them though gluetun I can just

ports:
  - 1235:1234

but using network_mode this cannot be done. What can I do? The only thing that comes to my mind is to use two gluetun containers, but I'd rather use a single one

thanks in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 4 days ago* (last edited 4 days ago) (1 children)

On mobile so you'll have to forgive format jank.

It depends how each image handles ports if C1 has the ports set up as 1234:100 and C2 has the ports set up as 1234:500 then:

service:

gluetun:

ports:
 - 1234:100 #c1
 - 1235:500 #c2
[...]

Will solve the conflict

Sometimes an image will allow you to edit it's internal ports with an environment so

service:

gluetun:

ports:
  - 1234:1000 #c1
  -1235:1234 #c2
c1:

environent:
- UI_PORT=1000
[...]

When both contsiners use the same second number, C1: 1234:80, C21235:80, and neither documents suggest how to change that port, I personally haven't found a way to resolve that conflict.

[–] [email protected] 2 points 3 days ago

thanks for the detailed reply!

When both contsiners use the same second number, C1: 1234:80, C21235:80, and neither documents suggest how to change that port, I personally haven’t found a way to resolve that conflict.

unfortunately I'm in this situation, so I guess my only ways are to modify the container by hand or to create two instances of gluetun. thank you very much for your help!