Whenever I run an apt-related step, I see this error message in the log:

<Date> DEBUG STDERR: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)

Should this be bind-mounted into the chroot?

Regards, Daniel


- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vmdb2 depends on:
ii  cmdtest         0.32.14.gcdfe14e-2
ii  debootstrap     1.0.126+nmu1
ii  e2fsprogs       1.46.5-2
ii  kpartx          0.8.5-2+b1
ii  parted          3.4-2
ii  python3         3.9.8-1
ii  python3-jinja2  3.0.1-2
ii  python3-yaml    5.4.1-1+b1
ii  qemu-utils      1:6.2+dfsg-1

Versions of packages vmdb2 recommends:
ii  ansible           2.10.7+merged+base+2.10.8+dfsg-1
ii  dosfstools        4.2-1
ii  qemu-user-static  1:6.2+dfsg-1

vmdb2 suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/lib/python3/dist-packages/vmdb/plugins/ansible_plugin.py (from vmdb2 package)
debsums: changed file /usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py (from vmdb2 package)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHm7MsACgkQS80FZ8KW
0F33UQ/+LkE7qXdvgdsIEVRGb8SXdzLQBQEEIaqkuCiWvfk//oRVy0uGPXvgb4kN
Iitl6B6MPfmLqDkYllSK6WGBrB+ykH2JbjziJ8SZpEdy6T4C+U7vdvVAnyuPEunM
V1ia4sPJZ+g8w+iM6v/OXnP61rlTVFmfWbwVP1TSN+mULdPi/4aftUVDwN+o7nuE
xFlBlQyhpFrJwCarlIj7LnLNp/kwjsgCnkZ7DakkhFUbQOr8d3AQefq0O/vH9UHt
xeE0hkz4wltsXSW5jryheLkWOmK1FFcrjGGv5JismU7cgOA2BbRixUEgd7aMPPOM
V6qMLU/qXvArTvhfY+0Vr+NAM2GS396AgbxlSoWerdojM0Ys4XAONlmOEReBXi2q
7gGxhlr861tAIjPxIYJkfFa2abWQFZSPXx3IsFUpuMjd543kKF1ERbJ14Lj66K29
3wRquvcCjzWrgdmvFPxRn/qnBpRle176LrxOSnL7lJNYCr4wtiBSd4Qr2MuCj7hQ
h9RGK/OQ7EM41Yc8/QAmXuKXn1HrJXGG9BY9Acv41an96q2nf0NV6+A5C1iHvV5I
V2ZBDp8WH8ieI29kU1oSAQsvs/NX6EBEWTeOPghNmys7C3XdHFNmZ+9W5maHH9F0
3RuiVdj4ZvHb8dljLtZzUwH+r9roIA6x3DBKff++hf9NBcuIbIk=
=piBa
-----END PGP SIGNATURE-----

Hello,

I confirm the same issue on vmdb2 recent :


ii  vmdb2                                  0.27+really.0.26-1
      all          creator of disk images with Debian installed

Is there one solution ?

Thanks in advance for you help

Cordialement

found 1003959 0.27+really.0.26-1
tags 1003959 + confirmed,upstream
thanks

Sory for taking so long to answer to this mail. I can just now only
confirm that the bug is present in my builds. However, as the upstream
author puts it, vmdb2 is "in selfish maintenance mode", so it is
unlikely he will develop a fix for this (but accepts patches!)

upstream
what log you need to debug ?
i try choot by debootstrap for use forky.

may be complet /etc/fstab