Repository navigation
boxd 0.4.69
A build host that reboots comes back by itself.
- After a reboot every
podcommand could fail withcurrent system boot ID differs from cached boot ID; an unhandled reboot has occurredandboxd-pod: podman ps failed. The build account has no runtime folder, so podman keeps its run state under the work area, on disk, and refuses to work after a reboot until two folders there are gone. The once-per-boot step of the build sshd (boxd-pod clear boot) now removes exactly those two folders before it clears the boxes. - Under runit the build sshd computed the memory cap before the zram service had switched its swap on, so the half of that swap that counts as memory was not taken off and the cap came out too high (about 2 GB on a 16 GB host). It now waits up to 30 seconds for the zram swap when the
zramenservice is enabled, and says so when it never comes. Under systemd the unit is ordered afterzramswap.service.