Agentome GitHub
Contents

Deploy on your server

This page is for the admin who puts Agentome on the company's own server, so that people's agents run there and not on their computers. It covers what the server needs, a Docker Compose install with places under gVisor, the same on Kubernetes, the network the agents get, and what to check before a pilot. The details of each step are in Operations; every setting is in Configuration.

What the server needs

Install with Docker Compose

Once gVisor is registered with Docker (step 2 below), one command does steps 1 and 3: it asks for the domain and whether places run here, and turns gVisor on for them.

curl -fsSL https://agentome.ai/install.sh | sh -s -- --domain agentome.example.com --places

By hand, or to see what it does:

  1. Install the server as in Getting started, and give it HTTPS: with a public name, the proxy profile gets a certificate from Let's Encrypt (HTTPS with the proxy profile); inside the company's network, use the company's certificate (HTTPS on a local network, A company certificate authority).

  2. Register gVisor with Docker in /etc/docker/daemon.json and restart Docker. The second runtime is for a run's own Docker (step 4), and only for it:

    {
      "runtimes": {
        "runsc": { "path": "/usr/local/bin/runsc" },
        "runsc-docker": {
          "path": "/usr/local/bin/runsc",
          "runtimeArgs": ["--net-raw", "--allow-packet-socket-write"]
        }
      }
    }
  3. Turn places on in .env, beside the settings of step 1, and start them:

    COMPOSE_PROFILES=proxy,places
    AGENTOME_PLACE_LAUNCHER_URL=http://place-launcher:8080
    AGENTOME_PLACE_RUNTIME=runsc
    docker compose up -d
  4. If your projects' tests start containers (testcontainers, a compose stack), give each run a Docker of its own, which lives inside gVisor and goes with the run:

    AGENTOME_PLACE_DOCKER_RUNTIME=runsc-docker
  5. If you want agents only on the server, and no person's computer to connect, add AGENTOME_COMPUTERS=false.

With more than a dozen places, give Docker smaller address pools, which must not overlap the company's networks: see Places on the server.

Install on Kubernetes

The manifests are in deploy/kubernetes of the release, with the places in the places component. In short:

  1. Install gVisor on the nodes and create its RuntimeClass, gvisor say.
  2. Set the namespace, AGENTOME_PUBLIC_URL and the image tag in kustomization.yaml, the certificate in ingress.yaml, and create the Secret with the secret key and the database's address.
  3. Take the places component and set AGENTOME_PLACE_RUNTIME=gvisor (the RuntimeClass's name). The cluster's network plugin must enforce NetworkPolicies: Calico and Cilium do.
  4. kubectl apply -k deploy/kubernetes, then open /setup with the setup code.

Every step is in Kubernetes. On Kubernetes a run has no Docker of its own yet: a project's databases come from its devcontainer, as its services.

The network agents get

A place and its runs have no way out but the egress proxy, which lets each through to what it needs and nothing else:

Who Reaches
The CLI, in a run's CLI container The model vendors and Agentome
Every command, in the run's sandbox Agentome and the hosts the task's project allows
A run's own Docker The hosts the project allows, for pulling images
The place itself, between runs The model vendors and npm, to install and sign in the CLI
A project's services (a database say) Nothing outside

An admin opens hosts per project in its Network section: the company's GitLab, Jira, a package mirror. Add public package registries adds npm, PyPI, Maven, Go, NuGet and Docker Hub at once, for a project without a mirror. A host a run was refused shows there for a week, with Allow beside it. The proxy lets a host through on port 443 unless the list names another, connects only to the address it checked, and reaches the company's own networks only for a host listed by its full name.

The proxy also connects to the server's own public name, for the CLI's gateway. Make sure the name resolves to an address the server's containers reach: on a network whose router does not loop a public address back inside, give the name an internal record, or an alias on the egress network (see Places on the server).

Keep it running

The install script's agentome command does these from any folder on the server:

Before a pilot

How runs are kept apart from what they must not reach is on Security.

Edit this page on GitHub