mirror of
https://github.com/johndoe6345789/docker-swarm-termina.git
synced 2026-04-24 13:45:01 +00:00
08d7ee16af
- Enhanced Docker connection diagnostics in backend - Detailed logging of Docker environment variables - Socket permission and existence checks - User/group information logging - Multiple connection attempt strategies - Automatic diagnostics on startup - Updated captain-definition with proper Swarm configuration - Added explicit Docker socket mount with read-write access - Configured User as root for socket access - Added DOCKER_HOST environment variable - Configured restart policy and replica settings - Updated Dockerfile to run as root for Docker socket access - Created comprehensive CapRover deployment documentation - Step-by-step deployment instructions - Troubleshooting guide - Security considerations - Architecture diagrams - Updated backend README with debugging and deployment info These changes fix the "Cannot connect to Docker" error by ensuring proper permissions and providing detailed diagnostics for troubleshooting. https://claude.ai/code/session_01NfGGGQ9Zn6ue7PRZpAoB2N
33 lines
653 B
Plaintext
33 lines
653 B
Plaintext
{
|
|
"schemaVersion": 2,
|
|
"dockerfilePath": "./Dockerfile",
|
|
"serviceUpdateOverride": {
|
|
"TaskTemplate": {
|
|
"ContainerSpec": {
|
|
"Mounts": [
|
|
{
|
|
"Type": "bind",
|
|
"Source": "/var/run/docker.sock",
|
|
"Target": "/var/run/docker.sock",
|
|
"ReadOnly": false
|
|
}
|
|
],
|
|
"User": "root",
|
|
"Env": [
|
|
"DOCKER_HOST=unix:///var/run/docker.sock"
|
|
]
|
|
},
|
|
"RestartPolicy": {
|
|
"Condition": "any",
|
|
"Delay": 5000000000,
|
|
"MaxAttempts": 0
|
|
}
|
|
},
|
|
"Mode": {
|
|
"Replicated": {
|
|
"Replicas": 1
|
|
}
|
|
}
|
|
}
|
|
}
|