diff options
| author | Helmut Grohne <helmut@subdivi.de> | 2025-05-06 11:50:31 +0200 |
|---|---|---|
| committer | Helmut Grohne <helmut@subdivi.de> | 2025-05-06 11:50:31 +0200 |
| commit | 0f2f563bedd683a9271fe32b158fb978861ae4d4 (patch) | |
| tree | 38ffd18dd7e712a0a4906bec9765db038274bb7c /useraddhook | |
| parent | 3affb25556fde51cf8574e51fbaa6ee025549c33 (diff) | |
| download | debvm-0f2f563bedd683a9271fe32b158fb978861ae4d4.tar.gz | |
debvm-create: fix network during mmdebstrap for old releases
We primarily run the systemd network stack inside debvm and that comes
with turning /etc/resolv.conf into a symbolic link. Unfortunately, we
may break networking during VM construction that way. The behavior is
quite release dependent.
For trixie and later, systemd-resolved.postinst takes a copy of
/etc/resolv.conf and places it at the symlink target.
For bookworm, systemd-resolved.postinst overwrites /etc/resolv.conf with
a link that becomes dead.
For bullseye and earlier, customize-resolved.conf overwrites
/etc/resolv.conf with a link that becomes dead.
That being dead means that passing any further customize hooks will not
be able to utilize networking as DNS resolution fails. To improve the
user experience, customize-resolved.sh will now turn ensure that those
symlink targets are reasonably popoulated.
Diffstat (limited to 'useraddhook')
0 files changed, 0 insertions, 0 deletions