Selfhosted

40187 readers

710 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

nginx proxy manager changes IP. How to get static container IP? (lemmy.ml)

submitted 7 months ago by [email protected] to c/selfhosted

25 comments fedilink hide all child comments

all the containers change IP addresses frequently. For home assistant a static IP address of the proxy manager is mandatory in order to reach it. For jellyfin it is useful to see which device accesses jellyfin. If the IP always changes, it doesn't work properly.

How do I fix a container IP with podman compose (or docker)

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

[–] [email protected] 5 points 7 months ago (2 children)

If you have everything in a compose stack, you can use the container name. Docker (and im sure podman) will do a dns resolution to the IP.
So you can use http://jellyfin:8000 instead of http://172.28.50.11:8000 (or whatever internal docker IPs are).
Not sure if it works outside of a compose stack. Might use different container name schemes (where inside a compose stack it would be "jellyfin", outside it might be "media-jellyfin-1" depending on folder names and various configs)

[–] ikidd 3 points 7 months ago

You need to create and specify a docker network to get different compose stacks to talk together directly. Default networks are separated between stacks, and have to bounce out to the host and back in, hence are only able to use the exposed ports of the target stack.

You can also specify the IPs that individual services use inside that network if you wish, but docker should handle name resolution within a network.

[–] [email protected] 2 points 7 months ago

So far I wasn't successful with that method in home assistant. I use that method in arr