Environments
An environment is a Docker endpoint sol2docker manages. Everything runtime resolves through an explicit environment — there is no ambient "global Docker". Standalone hosts and Swarm clusters are separate surfaces, detected live from the daemon.
The built-in local environment
The Docker socket you mount into the container becomes the built-in local environment. From
there you can add, edit, and remove more endpoints.
Connection types
| Type | Address | Notes |
|---|---|---|
| Unix socket | /var/run/docker.sock | The mounted local daemon. |
| TCP | tcp://host:2375 | Plain, unauthenticated — flagged as insecure in the UI. |
| TLS client-cert | tcp://host:2376 | Mutual TLS; cert/key stored encrypted at rest. |
| SSH | ssh://user@host | Key or agent auth; material stored encrypted. |
TLS and SSH material is encrypted with your SOL2DOCKER_ENCRYPTION_KEY
and is write-only — it never appears in API responses, job logs, or the audit trail.
Health & the fleet
- Health is a live ping plus engine version; standalone vs Swarm is detected from the daemon.
- Tags and search organize many endpoints.
- The cross-environment dashboard rolls up counts and reachability across the fleet.
- Uptime / health history persists reachability transitions, so you see "N outages / 7d".
A background poller checks reachability roughly every 45 seconds and records transitions; unreachable endpoints can raise a notification.
The Docker Engine API is per-node: a Swarm manager sees cluster-level objects but only its own node's local resources. To see every node's real state (images, live CPU/RAM), deploy the node agent.