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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
You declare the ip in your setup, or in the yaml file. An example for the docker-compose file is in the link below. I'd expect you'll want to declare the network and such as well, if you're not familiar.
https://gist.github.com/natcl/3d881d00a56c8a961e6dab8ba51a5a37
It worked, thank you
This was a fast response, and doesn't cover the whole scope of handling networking in docker. As mentioned elsewhere there is a different network philosophy for Standalone Containers & Overlay networking.
Thx. That helps a lot
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)
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.
So far I wasn't successful with that method in home assistant. I use that method in arr
A container does not have an IP, only a network card has an IP. Containers normally use a specific port which normally is not changing like 8080 or 8123, etc. I think you misunderstood something with your setup.
The containers all have IPs unless you use the "host" network type, in which case it just stays in the host namespace, or "none" which ends up with an empty network namespace. And the IPs can indeed change. This is also why multiple containers can bind to the same port without colliding with eachother.
Docker kind of hides it from you because when you use -p to publish a port, it sets up a proxy process for you to pass traffic from the port on the host to the port on the container.
You usually have a docker0 bridge with an IP like 172.16.0.1, and if you run ip a in a container it'll have a single interface with an IP of 172.16.0.2.
Those are just the basic ones too, when macvlan, macvtap, ipvlan gets involved it gets even crazier. You can directly attach containers to the network such that your router assigns it an IP via DHCP like it's just another device plugged on your network.
You can also share a network namespace with multiple containers, usually kubernetes/podman pods to enable for sidecar containers like Filebeat, Consul, Envoy, etcd and so on.
If you use rootless containers, it'll use slirp4netns to emulate the network entirely in userspace.
In the cloud you usually end up with your pods directly attached to your VPC as well, like AWS Fargate serverless offerings.
Inside the virtual docker network they do have temporary IPs and hostnames. But it is pointless to reference these IPs, just use the hostnames which should be identical to the container name.
I rather worded it poorly
Nah. Your question was fine. The person who responded to you was just wrong. Hopefully you've seen the other replies to their comment.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DHCP | Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network |
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| VPN | Virtual Private Network |
| nginx | Popular HTTP server |
[Thread #645 for this sub, first seen 31st Mar 2024, 09:55] [FAQ] [Full list] [Contact] [Source code]
nginx is no acronym or other shit you bad bot :P
You can specify a fixed IP range for a container in the private address space instead of letting Docker pick one. You can also pick a specific IP on that range for each container. You can also attach to the host public interface and get an IP from your LAN DHCP, or pick a MAC adress so you can get the same IP address each time from DHCP (as well as a name on the LAN DNS if you want).