docker-container-access

When localhost access fails in DinD or DooD environments, you must detect the active Docker context to determine the correct container access method. This skill identifies whether you are on a host, DinD, or DooD setup and provides the appropriate access commands for your specific environment.

DinD (Docker-in-Docker) runs a Docker daemon inside a container, while DooD (Docker-outside-of-Docker) accesses the host daemon. Container connectivity and file-sharing methods differ significantly between them, requiring environment detection to choose the correct approach for cross-environment operation.

To use curl for container-to-container connectivity, you need to first detect your Docker environment (host, DinD, or DooD) to identify the correct network address. This skill provides practical curl examples and access commands tailored to your specific Docker context.

Yes, Playwright MCP works with DooD setups, but you must apply the correct environment detection steps first. This skill specifies the requirements for cross-environment operation and provides guidance and examples for using Playwright MCP safely within DooD contexts.

In DooD environments, bind-mount sharing has specific caveats due to differing file path resolutions between the host and the container. This skill provides DooD-friendly sharing guidance to help you navigate these file-sharing considerations and avoid common path-mapping pitfalls.