ywc-docker-isolate

Prevent Docker host-port collisions in parallel Git worktrees by deriving deterministic, per-worktree port blocks and project names. This manages isolation via local environment files without modifying committed compose or environment configuration files.

Deterministic Docker port isolation is a technique that derives unique host-port blocks and project names based on the task name. It eliminates the 'port is already allocated' error by managing environment-local port mappings across concurrent stacks.

Apply port isolation to Docker Compose stacks by managing isolation via local environment files. This approach maintains immutable infrastructure by never modifying your committed compose or environment configuration files.

Yes, Docker port isolation works with multi-task development environments using Docker Compose where concurrent stacks are required. It requires bash, docker, python3, and git to manage environment-local port mappings and container lifecycles.

Audit and clean up stale Docker containers across multiple worktrees using integrated teardown and audit capabilities. These lifecycle management features ensure clean Docker environments and prevent stale, resource-hogging containers from persisting.

Running multiple Docker Compose stacks in different worktrees causes 'port is already allocated' errors because concurrent stacks attempt to bind to the same host ports. Deriving unique, per-worktree port blocks eliminates these collisions.