# Running the MPC Launcher in Non-TEE Mode

This guide describes the **high-level steps** required to run the MPC launcher **outside of a TEE**, using the same launcher and MPC Docker images as in TEE deployments.

The goal is to allow developers and operators to exercise the **real production launcher flow** (image selection, validation, container launch, upgrades) **without relying on TEE / dstack infrastructure**.

---

## Overview

In non-TEE mode:
- The launcher runs with `PLATFORM=NONTEE`
- No dstack socket or attestation is used
- RTMR extensions are skipped
- Image hash validation and upgrade logic remain unchanged
- The MPC container is launched **without** `DSTACK_ENDPOINT` and without the dstack socket mount

This provides maximum parity with production while keeping the setup simple.

---

## Prerequisites

- Docker installed and running
- Docker Compose (classic `docker-compose` or plugin `docker compose`)
- Network access to pull Docker images
- A valid MPC Docker image digest

---

## Files Used

- **Launcher Docker Compose (non-TEE):** `deployment/cvm-deployment/launcher_docker_compose_nontee.yaml`

- **User configuration file:** `user-config.toml` (TOML format, mounted at `/tapp/user_config`)

---

## Step-by-Step Instructions

### 1. Prepare the non-TEE docker-compose file

Create or use a non-TEE launcher compose file with the following properties:

- Set `PLATFORM=NONTEE`
- Mount `/var/run/docker.sock`
- Do **not** mount `/var/run/dstack.sock`
- Mount the user config file at `/tapp/user_config`
- Provide persistent volumes for shared state and MPC data

See `deployment/cvm-deployment/launcher_docker_compose_nontee.yaml` for an example.

---

### 2. Prepare the user configuration file

Create a `user-config.toml` file (TOML format) with `[launcher_config]` and `[mpc_node_config]` sections. The `[launcher_config]` section uses an `image_reference` field for the Docker image reference (e.g., `image_reference = "nearone/mpc-node"`).

For the non-TEE / local-dev launcher path, use **`deployment/cvm-deployment/ci-config.toml`** as the starting point — it boots cheaply on a small machine using mainnet's embedded genesis. The sibling **`deployment/cvm-deployment/user-config.toml`** is a real testnet operator template with `chain_id = "testnet"` and `download_genesis = true`, which downloads the multi-GB testnet genesis at startup and OOMs small CI/dev runners (see #2720).

This file is read by the launcher and passed into the MPC container.

---

### 3. Start the launcher

From the directory containing the non-TEE compose file:

```bash
docker-compose -f launcher_docker_compose_nontee.yaml up -d
```

---

### 4. Monitor launcher logs

```bash
docker logs -f launcher
```

You should see:
- `Launcher platform: NONTEE`
- Image hash selection and validation
- `PLATFORM=NONTEE → skipping RTMR3 extension`
- The MPC container being launched via `docker compose up -d`

---

### 5. Verify the MPC container

Check that the MPC container is running:

```bash
docker ps
```

Inspect the MPC container to confirm:
- No `DSTACK_ENDPOINT` environment variable exists
- No dstack socket is mounted
- Expected ports are published

Example:
```bash
docker inspect mpc-node
```

---

## Stopping and Restarting

Stop and remove containers:
```bash
docker-compose -f launcher_docker_compose_nontee.yaml down
```

Stop and remove containers **and volumes** (full reset):
```bash
docker-compose -f launcher_docker_compose_nontee.yaml down -v
```

Restart:
```bash
docker-compose -f launcher_docker_compose_nontee.yaml up -d
```

---

## Notes

- Non-TEE mode is intended for **testing, development, and debugging**
- Security-sensitive behavior for TEE deployments remains unchanged
- The same launcher image and MPC image hashes are used in both modes

---