zrlhk
June 27, 2025, 3:44pm
1
Hi guys. I have a very strange problem.sometimes, the containers got two IPs.
When I restart it, maybe 1 minitues later, the container got another IP like “169.254.xx.xx”
I have export the images here: http://hseek.eu.org/d11.tar.gz
BYW: this images is based Debian11 and with lxde installed.
I have testing many times, and can’t fix this problem. thanks for helping.
stgraber
(Stéphane Graber)
June 27, 2025, 4:35pm
2
169.254.x.x
is a link-local IPv4 address, that’s self-assigned by the guest, not something we’d be pushing over DHCP or the like.
So that’s going to be because of some kind of configuration inside of your container.
zrlhk
June 27, 2025, 11:18pm
3
yes, I have googled about this problem. And I did not make any configuration in the container.
I named it as a strange problem, because I made other image with same steps, but some container is ok, some have this problem.
The steps I made it like: install xrdp+lxde,remove libreoffice*. There are no other special operations.
I tried to modify the mac address of the container, operate in the Debian11/12 OS container, and change the host system to ubuntu/debian, but the problem still persisted.
So I hope guys import this image to help analyze the problem. Thanks.!
stgraber
(Stéphane Graber)
June 28, 2025, 2:28am
4
Not likely to have much time to try that in a little while as I’m traveling but normal networking rarely messes with link-local stuff, so my best guess is that you installing desktop stuff in there has pulled something like Network Manager or an equivalent into your system which is now making a bit of a mess.
zrlhk
June 28, 2025, 8:03am
5
Hope you can enjoy your journey. Thank you for your reply. I will continue to try to change the installed desktop.
simos
(Simos Xenitellis)
June 28, 2025, 8:22am
6
It should be easy to add the appropriate service to a container and get the link-local special address.
The stock container images should not be affected.
zrlhk
July 1, 2025, 1:02pm
7
This is the relevant log. I hope it can be helpful in solving this problem:
Jul 01 12:54:41 d11 dbus-daemon[168]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
Jul 01 12:54:41 d11 systemd[1]: Started PackageKit Daemon.
Jul 01 12:54:56 d11 dbus-daemon[168]: [system] Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)
Jul 01 12:54:56 d11 systemd-networkd[157]: Could not set hostname: Method call timed out
Jul 01 12:54:56 d11 systemd-networkd[157]: Could not set hostname: Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)
Jul 01 12:54:56 d11 systemd-networkd[157]: Could not set hostname: Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)
Jul 01 12:55:11 d11 avahi-daemon[166]: Registering new address record for 169.254.84.18 on eth0.IPv4.
Jul 01 12:55:11 d11 connmand[169]: eth0 {add} address 169.254.84.18/16 label eth0 family 2
Jul 01 12:55:11 d11 connmand[169]: eth0 {add} route 169.254.0.0 gw 0.0.0.0 scope 253
Jul 01 12:55:11 d11 connmand[169]: eth0 {add} route 0.0.0.0 gw 0.0.0.0 scope 253
Jul 01 13:21:39 d11 systemd[1]: Starting Hostname Service…
Jul 01 13:21:39 d11 systemd[1184]: systemd-hostnamed.service: Failed to set up network namespacing: Permission denied
Jul 01 13:21:39 d11 systemd[1184]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied
Jul 01 13:21:39 d11 systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Jul 01 13:21:39 d11 systemd[1]: systemd-hostnamed.service: Failed with result ‘exit-code’.
Jul 01 13:21:39 d11 systemd[1]: Failed to start Hostname Service.
Jul 01 13:22:04 d11 dbus-daemon[168]: [system] Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)
Jul 01 13:23:56 d11 dbus-daemon[168]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’ requested by ‘:1.33’ (uid=0 pid=1188 comm="hostnamectl status ")
Jul 01 13:23:56 d11 systemd[1189]: systemd-hostnamed.service: Failed to set up network namespacing: Permission denied
Jul 01 13:23:56 d11 systemd[1]: Starting Hostname Service…
Jul 01 13:23:56 d11 systemd[1189]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied
Jul 01 13:23:56 d11 systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Jul 01 13:23:56 d11 systemd[1]: systemd-hostnamed.service: Failed with result ‘exit-code’.
Jul 01 13:23:56 d11 systemd[1]: Failed to start Hostname Service.
Jul 01 13:24:21 d11 dbus-daemon[168]: [system] Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)
Jul 01 13:25:22 d11 systemd[1]: Reexecuting.
Jul 01 13:25:26 d11 dbus-daemon[168]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’ requested by ‘:1.37’ (uid=0 pid=1323 comm="hostnamectl status ")
Jul 01 13:25:26 d11 systemd[1]: Starting Hostname Service…
Jul 01 13:25:26 d11 systemd[1324]: systemd-hostnamed.service: Failed to set up network namespacing: Permission denied
Jul 01 13:25:26 d11 systemd[1324]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied
Jul 01 13:25:26 d11 systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Jul 01 13:25:26 d11 systemd[1]: systemd-hostnamed.service: Failed with result ‘exit-code’.
Jul 01 13:25:26 d11 systemd[1]: Failed to start Hostname Service.
Jul 01 13:25:35 d11 systemd[1]: Received SIGTERM from PID 1180 (bash).
Jul 01 13:25:35 d11 systemd[1]: Reexecuting.
Jul 01 13:25:51 d11 dbus-daemon[168]: [system] Failed to activate service ‘org.freedesktop.hostname1’: timed out (service_start_timeout=25000ms)