Problem
Kubernetes scenarios that use kind (Kubernetes in Docker) fail because the scenario containers don't have access to the Docker daemon.
Current Behavior
- Scenario containers are started without the Docker socket mounted
- When
kind create cluster runs inside the container, it fails with "Cannot connect to the Docker daemon"
Expected Behavior
- Scenario containers should have Docker access to create and manage kind clusters
- The
kind command should successfully create local Kubernetes clusters
Root Cause
The server starts containers with:
docker run -it --rm --name devops-dojo-${socket.id} --network devops-dojo-net ${imageName}
Missing the required Docker socket mount: -v /var/run/docker.sock:/var/run/docker.sock
Solution
Add Docker socket mounting to the container creation command in src/server/index.ts
Impact
All Kubernetes scenarios are currently non-functional
Problem
Kubernetes scenarios that use
kind(Kubernetes in Docker) fail because the scenario containers don't have access to the Docker daemon.Current Behavior
kind create clusterruns inside the container, it fails with "Cannot connect to the Docker daemon"Expected Behavior
kindcommand should successfully create local Kubernetes clustersRoot Cause
The server starts containers with:
Missing the required Docker socket mount:
-v /var/run/docker.sock:/var/run/docker.sockSolution
Add Docker socket mounting to the container creation command in
src/server/index.tsImpact
All Kubernetes scenarios are currently non-functional