this post was submitted on 14 Jul 2023
11 points (82.4% liked)

Selfhosted

40323 readers
655 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi, I figured out how to get docker containers to join an existing network with putting "networks" into the respective sections of the docker-compose.yml

If I want to also give them fixed ip's on this network, what would the syntax look like in the docker-compose.yml?

you are viewing a single comment's thread
view the rest of the comments
[–] NewDataEngineer 1 points 1 year ago* (last edited 1 year ago)

What I haven’t figured out yet is whether or not I can give my docker services their own IP on my router for access from another system on a fixed or reserved IP.

You can. You have to set up a macvlan on your network and then assign an IP to your container that sits on your router's subnet.

I can only use traefik with a macvlan because Synology DSM uses ports 80 and 443. I assign traefik its own IP and use pihole's DNS to route wildcard subdomain to it.

I wrote a guide in my trillium notes. If you're interested I can share.