No notifications
Peer-to-peer Docker control plane over HyperDHT and protomux-rpc. No central server. No cloud account.
A short tour of what to do next:
Overview
Live engine health, storage, and activity on the active peer
Templates, compose stacks, and custom images
Lifecycle, logs, stats, and terminals
| Name | Image | Status | CPU (%) | Memory (MB) | IP Address | Actions |
|---|
Local image inventory and actions
| Repository | Tag | Image ID | Size | Created | Usage | Actions |
|---|
Bridge, overlay, and container networks
| Name | Driver | Scope | Subnet | Gateway | Containers | Actions |
|---|
Stats charts will be displayed here
Compose stacks on the remote host
| Stack Name | Services | Containers | Status | Actions |
|---|---|---|---|---|
| No stacks found. Deploy a stack to get started. | ||||
Persistent storage volumes
| Name | Driver | Mountpoint | Usage | Actions |
|---|
Concurrent multi-host health and Docker status
Peer invites, revoke list, registry vault
Live Docker engine activity on the active peer
Engine info, capacity, and process metrics
Client preferences and peer context
Portainer-format JSON catalogs (templates.json). Add as many as you want — peardock merges them and removes duplicates (same image / stack repo / title). Portainer only allows one list.
Clear all configured peers from this client. You will need to re-add public keys to connect again.
peardock — decentralized Docker control plane over HyperDHT.
Keyboard: Ctrl+K command palette · ? shortcuts
Are you sure?
This form was replaced by the smart Create network dialog.