Le 2/18/25 à 11:53, Yassine Chaouche a écrit :
Hello all,
I have been advised to use systemd-nspawn and machinectl in place of chroot to
run services from a cloned, working remote host.
Another interresting behavior is when I start it with the UID shifting feature
-U
$ systemd-nspawn -bU
For services/sockets your best bet might be to simply bind them to 0.0.0.0
such that they still work after the address change.
My solution for the DNS record is to use iproute2 tools which provide a
monitor command (in the sample below filtered for IPv6 changes):
#!/usr/bin/sh
touch "$CACHE_DIREC
On Wed, Feb 19, 2025 at 01:54:06AM +0100, Thomas Köller wrote:
> While address updates using systemd's DHCP client seem to work just fine,
> there is a problem, however. Whenever the host's IP address changes, some
> reconfiguration has to be done: running services listening on sockets opened
> bef
