Open osmith42 opened 2 years ago
Actually the problem was, that lxc.conf did not have lxc.pty.max
.
Once we added lxc.pty.max = 1024
on the obs server host, in /var/lib/lxc/obs/config
and restarted the obs workers to download the new config from the server, it worked: /dev/ptmx
appeared inside the lxcs started by the workers, and the testsuite using ptys didn't fail anymore.
Maybe this should be added in the default lxc.conf?
Using lxc as build environment, a package that tries to run a testsuite during the build process fails with:
The same package can be built fine on the public OBS.
I've looked into the lxc spawned by obs-worker with lxc-attach while a build was running, and /dev/ptmx is missing. I assume something like the following needs to be added to
vm_detect_2nd_stage
inbuild-vm
?versions and setup
obs-worker:
obs-server:
obs-worker is running inside an lxc, and is configured to use lxc as build environment. So it starts an inner lxc container for each build. In the outer lxc container, it is possible to use pseudo ttys, /dev/ptmx and /dev/pts are available and working as expected.