The server list shows hostnames, roles, addresses, resources, state, and labels. Hostnames can repeat; use the server ID and address to identify a specific machine.
Join a server
- As an Admin, open servers and select the Worker or Manager join command.
- Check the target machine’s requirements and connectivity.
- Run the provided command on that machine.
- Refresh the list and verify Ready state, role, and address.
- Add labels before placing applications.
Workers run workloads; Managers also participate in management. Join credentials are reusable for 30 minutes. Obtain a fresh command after platform restart or expiry; changed issuer permissions can also invalidate it. Do not publish the credential.
Read state
Ready, Down, and Disconnected describe runtime connectivity. Active accepts scheduling; Pause does not accept new tasks; Drain indicates draining. Manager reachability is a separate management status. Collector warnings indicate stale observations and should be checked separately.
Check current capacity in server metrics.
Remove carefully
Removal does not migrate applications, back up volumes, or drain the server for you. Check fixed-server applications, local data, platform components, remaining capacity, and management availability first.
Removing the record does not erase local volumes or confirm that containers on an offline machine stopped. Rejoining may produce a new ID, requiring fixed-server selections and labels to be reviewed.
For join failures, inspect the address, credential, Docker state, ports, and firewalls. Browser access alone does not verify server-to-server communication.