Run command in chroot, Couldn't resolve host name, systemd
Helmut Schneider
jumper99 at gmx.de
Sat Apr 27 09:07:28 UTC 2024
Am 27.04.2024 um 10:42 schrieb Manuel Trier via ubuntu-users:
> I've found a similar issue in the manjaro forum, maybe it's worth a look...
>
> https://forum.manjaro.org/t/no-dns-resolution-in-chroot-qemu/45306/7
> <https://forum.manjaro.org/t/no-dns-resolution-in-chroot-qemu/45306/7>
>
> For me it looks like this matches your issue
Good catch, worked!
Apr 27 11:00:14 mail2 freshclam[131873]: freshclam daemon 0.103.11 (OS:
linux-gnu, ARCH: x86_64, CPU: x86_64)
Apr 27 11:00:14 mail2 freshclam[131873]: Sat Apr 27 11:00:14 2024 ->
ClamAV update process started at Sat Apr 27 11:00:14 2024
Apr 27 11:00:14 mail2 freshclam[131873]: ClamAV update process started
at Sat Apr 27 11:00:14 2024
Apr 27 11:00:22 mail2 freshclam[131873]: Sat Apr 27 11:00:22 2024 ->
daily database available for download (remote version: 27258)
Apr 27 11:00:22 mail2 freshclam[131873]: daily database available for
download (remote version: 27258)
Apr 27 11:00:32 mail2 freshclam[131873]: Sat Apr 27 11:00:32 2024 ->
Testing database:
'/var/lib/clamav/tmp.c80e436bbc/clamav-9b07a608ce4d5c09c16e6086eeb83b26.tmp-daily.cvd'
...
Now I need to find out, what exactly is required as mounting only
/run/systemd/ and /run/resolvconf/ is not enough.
Thank you!
More information about the ubuntu-users
mailing list