pibo-docker-system

Isolate Pibo code execution in Docker by spawning compute workers using the CLI, which creates dedicated containers and Git worktrees. This ensures environment separation from the host system during development and testing.

Docker compute workers are used to execute Pibo code in isolated environments. They support Git worktree management, Docker image builds, and worker lifecycle operations, ensuring development changes do not affect the host system.

Yes, you need both Docker and Pibo CLI installed to use isolated compute workers. Docker provides the container environment for execution, while the Pibo CLI manages worker spawning, rebuilding, and lifecycle operations.

Spawn a Docker worker with a specific Git branch for testing by running the command `pibo compute dev spawn --worktree <branch-name>`. This creates an isolated environment with the specified branch checked out.

Yes, you can manage the full Docker worker lifecycle including spawning, rebuilding, releasing, and reaping. The system defines clear boundaries for Docker worker and host gateway operations to maintain isolation.

Yes, Pibo Docker isolation supports development authentication and browser validation for Docker workers. This facilitates testing authentication flows and validating browser interactions within the isolated compute environment.