…and more importantly, where is that setting stored so I can turn it on for all of them?
I realize this varies according to OS, so I’m specifically asking about my Turnkey Nextcloud and Turnkey Mediaserver containers, which are based on Debian Linux. It’s perhaps worth noting that my Turnkey Syncthing container, which uses the same base OS, does register its hostname with my DHCP server. I’ve gone digging around in /etc/ etc. in each of the containers, but so far I haven’t found any configuration differences that would explain the difference in behavior. (Also, if it matters, my DHCP server is the one included with OpenWRT and running on my router.)
By the way, I’m aware that the best answer might be “you have an X/Y problem and you really ought to use static IPs and/or setup a reverse proxy,” but I haven’t gotten to that point yet. Besides, I still want to satisfy my curiosity about DHCP and hostnames regardless.
EDIT: to be clear, this post is about LXC containers running directly in Proxmox, NOT Docker.
Where is that DHCP server? Are you sure they get actual DHCP leases?
Typically Docker’s internal resolution is basically just injecting the hostnames in /etc/hosts, but Docker also supports macvlan and macvtap networks too which can expose a container network directly on the network.
But I think 99% of containers just use the default bridge network. I never heard of a Docker container running a DHCP client, most containers run the app process directly and don’t do a full boot.
Where is that DHCP server? Are you sure they get actual DHCP leases?
The DHCP server is dnsmasq running on my OpenWRT router.
The “Active DHCP Leases” table has entries for the Syncthing and the Nextcloud containers (the former with the hostname listed as “syncthing” and the latter with it listed as “?”). Weirdly, it does not have an entry for the Mediaserver container, even though that container is getting a valid IP.
I also looked through the system logs and found DHCP-related messages for each (Nextcloud is .120, Mediaserver is .159, and Syncthing is .191):
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
Where is that DHCP server? Are you sure they get actual DHCP leases?
Typically Docker’s internal resolution is basically just injecting the hostnames in
/etc/hosts, but Docker also supports macvlan and macvtap networks too which can expose a container network directly on the network.But I think 99% of containers just use the default bridge network. I never heard of a Docker container running a DHCP client, most containers run the app process directly and don’t do a full boot.
The DHCP server is dnsmasq running on my OpenWRT router.
The “Active DHCP Leases” table has entries for the Syncthing and the Nextcloud containers (the former with the hostname listed as “syncthing” and the latter with it listed as “?”). Weirdly, it does not have an entry for the Mediaserver container, even though that container is getting a valid IP.
I also looked through the system logs and found DHCP-related messages for each (Nextcloud is .120, Mediaserver is .159, and Syncthing is .191):
Again, this post is about LXC containers running directly in Proxmox, NOT DOCKER.