3.8 KiB
3.8 KiB
Tux-Dock Development Log
0.2-beta
This release introduces tuxreaperd, a micro init system for containers.
Micro init
- Split the reaper into two implementations:
tuxreaperdgnu.c: the original standard POSIX/libc daemon used as PID 1 inside containers created by tux-dock.tuxreaperdasm.c: a new freestanding-nostdlibsyscall engine forx86_64andaarch64with a tiny static footprint.
- Both run as subreapers (
PR_SET_CHILD_SUBREAPER) with a SIGCHLD handler that reaps every reparented/terminated descendant, so orphaned processes never accumulate as zombies. - Both forward SIGTERM/SIGINT/SIGHUP to the primary workload and propagate its exit status (128 + signal for signal deaths).
compile.shdetects the host architecture and builds the freestanding implementation when possible, falling back totuxreaperdgnu.con failure or unsupported hosts.DockerManager::createContainerbind-mountstuxreaperdinto the container as PID 1 and resolves the binary next to thetux-dockexecutable when it is not in the current directory.
Tests
- Added
tuxreaperd-zombie-tests, an in-container test suite that boots a container withtuxreaperdas PID 1 and verifies orphaned grandchildren are reaped (zero zombies), exit status is propagated, anddocker stopcleanly shuts down via forwarded SIGTERM (exit 143). - The HTML web test view now includes a "Tuxreaperd Zombie Reaping" section alongside the Docker integration and TUI transcript sections.
0.1.2-beta
This release adds signal trapping to prevent state corruption during long-running Docker operations.
Reliability
- Added SIGINT (Ctrl+C) signal trapping during busy operations to prevent premature exit and socket corruption
- Added SIGTSTP (Ctrl+Z) signal trapping during busy operations to prevent suspension mid-operation
- Signals chain to previous handlers when not busy, preserving normal exit and suspend behavior
- Trap re-installs after terminal I/O restoration cycles to maintain protection through Attach Shell sessions
- Used SA_RESTART flag to prevent EINTR on blocking socket reads during signal delivery
TUI
- Added visual feedback in busy modal when signals are trapped
- Shows "Ctrl+C ignored: operation in progress" when SIGINT is trapped
- Shows "Ctrl+Z ignored: operation in progress" when SIGTSTP is trapped
0.1.1-beta
This release establishes the first beta-quality Docker integration and TUI workflow.
Docker integration
- Added direct Docker Engine API access through
/var/run/docker.sock. - Added startup Docker preflight using
GET /_pingbefore launching the TUI. - Added synchronous initial container and image loading.
- Added asynchronous cache refreshes after mutations and interactive sessions.
- Preserved cached state when a refresh fails.
- Added structured container/image JSON mapping with exited-container support.
Process execution
- Replaced
system()andpopen()with afork/execprocess runner. - Added captured stdout/stderr and inherited terminal I/O modes.
- Kept direct CLI execution for interactive terminal handoffs.
Reliability
- Added HTTP response parsing for Content-Length, chunked transfer, and bodyless responses.
- Added robust handling for Docker
204and idempotent304responses. - Added tri-state stop polling: stopped, running, and unknown.
- Added bounded stop retries after transport timeouts.
- Stop completion now refreshes cached state before showing the result modal.
TUI
- Replaced the persistent status panel with a centered actions panel.
- Added busy-operation modals with spinner feedback.
- Blocked input during long-running Docker operations.
- Added structured, scrollable container and image list dialogs.
Tests
- Added HTTP response parser tests.
- Added container JSON mapping tests.
- Added operation-state tests.
- Added stop polling and timeout-sequence regression tests.