• WslDock

Exploring the Concept

The solution revealed itself through a simple but powerful command: wsl -d <instance> sleep infinity. This elegant approach keeps the WSL instance alive by running a process that never terminates. It’s the kind of solution that feels obvious in hindsight—using the system’s own mechanisms rather than fighting against them.

The elegance of sleep infinity

Unlike simulated input or complex workarounds, sleep infinity operates at the process level. It tells the Linux kernel that the instance should remain active indefinitely, which is exactly what we need for development environments.

The command is:

• Minimal: No external dependencies, no complex setup
• Transparent: The process is visible in the task list, making it easy to understand
• Reversible: Stopping the process immediately returns the instance to its normal lifecycle

Beyond Persistence: SSH Tunnels

But keeping the instance alive was only half the picture. The real value emerged when I considered SSH agent forwarding. With a persistent WSL instance, I could maintain SSH tunnels to remote servers, keeping my development tools connected without constant re-authentication.

Using sleep infinity represents a fundamental principle in systems programming: work with the system, not against it. Instead of creating complex workarounds to prevent WSL from shutting down, we simply tell it to stay active. This approach respects the system’s design while achieving our goal—clean, maintainable, and transparent.