Get started
DocsComputes / Manage a Compute

Computes

Manage a Compute

Check a Compute's health, update it, share it, and fix one that's offline, has no engine or lost its identity.

Updated

View as Markdown
On this page

Every Compute has a page in the Console: open Computes and pick it. It shows the Compute's health, its hardware, its Instances and its members. When something needs you, a notice at the top says what and how to fix it.

What the page tells you#

Notice What it means What to do
name hasn't connected yet It enrolled, but its client isn't running On a desktop computer, open the Uremot app. On a server, start the service, or run uremot compute run for a per-user install
Nothing can run on name yet It's online, but no container engine answers there Install or start the engine; How to install links to it. The Compute finds it within a few seconds
Needs update Its client is too old to keep restarting agent desks safe. Until it's updated, the platform changes nothing on it Update it (below)
Paused by your plan Your organization has more Computes than its plan allows, so nothing runs on this one Upgrade, remove a Compute, or press Keep this Compute to run it and pause another instead. Nothing is deleted

Update its client#

When a newer release is out, the Compute's page offers Update, if its client can update itself. Confirm with Update to version: the Compute restarts its Uremot client, and running Instances keep running. Only people who may manage the Compute see Update. If the update fails, the page says why and offers Try again.

Otherwise the page says to run uremot update on the Compute:

Terminal
uremot update

Share it with people#

Members lists the people with access to this Compute beyond the workspace's own members. Press Add member to give someone access. A Compute you enrolled with Shared with your workspace is open to every member and their agents already (Add a Linux server).

Fix a Compute#

From the machine, uremot compute status tells you most of what's wrong: the identity, whether a container engine answers, and whether the service runs.

  • Offline. On a service install, run sudo systemctl enable --now uremot-compute, and read journalctl -u uremot-compute if it stays down. Otherwise, run uremot compute run and keep it running.
  • Docker is installed, but this user can't reach it. Add yourself to the docker group (sudo usermod -aG docker $USER), log out and in, then start uremot compute run or the desktop app again.
  • Lost its identity, for example after a reinstall. To keep its Compute record, press Create recovery grant on its page, under Recovery grants, and run the command it shows, uremot compute recover --grant-stdin. Or start over: stop it, run uremot compute reset, and enroll again.

Remove it#

Under Danger zone, Archive… takes the Compute out of the workspace, and nothing can be launched on it. A Compute with active Instances can't be archived, so archive those first. On the machine, uremot uninstall removes the binary and the service.

For your AI#

The uremot-computes skill checks and repairs a Compute step by step, from the platform and on the machine: uremot-computes.