> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Linux

Every sandbox is a Linux virtual machine booted from an OCI image, never a container that shares the host's kernel. The image provides the userland. The platform provides the kernel, the first process, and the disks.

## Control Plane Support

A Linux sandbox supports every operation of the common control plane, through the API or the `telnyx-edge` CLI.

| Operation | Linux |
| - | - |
| [Create](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/creation.md) | Yes, from a `linux/amd64` OCI image, a template, or a snapshot |
| [Batch create](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/creation.md#batch-create) | Yes, up to 10 sandboxes at once |
| [List, read, and update](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/operations.md) | Yes |
| [Pause and resume](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/user-controlled-lifecycle.md#pause-and-resume) | Yes, with memory, processes, and disks kept |
| [Connect](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/user-controlled-lifecycle.md#connect) | Yes |
| [Terminate](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/user-controlled-lifecycle.md#terminate) | Yes |
| [Wait](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/user-controlled-lifecycle.md#wait) | Yes |
| [Fork](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/user-controlled-lifecycle.md#fork) | Yes, up to 20 sandboxes with the source's live state |
| [Snapshots](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/snapshots.md) | Yes, of memory and disks |
| [Templates](https://developers.telnyx.com/docs/edge-compute/sandboxes/organization-resources/templates.md) | Yes, with a ready-state checkpoint |
| [Timeout and idle timeout](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/platform-managed-lifecycle.md) | Yes |
| [Paused retention](https://developers.telnyx.com/docs/edge-compute/sandboxes/common-control-plane/platform-managed-lifecycle.md#paused-retention) | 7 days |

## Virtual Machine

| Component | Description |
| - | - |
| Kernel | A Linux kernel provided by Telnyx. It loads no modules. |
| First process | A Telnyx init process, which runs execs, serves files, and supervises the main command. |
| Root disk | `/`, ext4, 8 GiB, built from the image. |
| Workspace disk | `/workspace`, ext4, 16 GiB. |
| Network | One IPv4 interface. No IPv6. |
| Architecture | x86-64. |

A disk that fills returns `ENOSPC` to the writing process. The sandbox keeps running.

## Image Requirements

* **Platform.** The image must offer `linux/amd64`. From a multi-platform index, the `linux/amd64` manifest is used.
* **Layers.** Layers are gzip-compressed or plain tar. zstd and foreign layers are refused.
* **Size.** The unpacked image must fit the 8 GiB root disk.
* **Registry.** The reference names its registry host. See [Templates](https://developers.telnyx.com/docs/edge-compute/sandboxes/organization-resources/templates.md#images).

The build drops extended attributes, so file capabilities set in the image are lost. Device nodes and FIFOs in the image are not created.

## Processes and Users

| Process | Runs As | Working Directory |
| - | - | - |
| Main `command` | The image's `USER` | `workdir`, else the image's `WORKDIR` |
| Exec | `root`, or the exec's `user` | The exec's `workdir`, else the sandbox's |
| File requests | `root` | Not applicable |

The image's `ENTRYPOINT` and `CMD` are never run. Root in a sandbox is root in its virtual machine only.

## Environment Variables

Each process receives its environment in layers. A later layer replaces an earlier variable of the same name.

1. The platform defaults: `PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin`, `HOME=/root`, `LANG=C.UTF-8`, and the certificate variables listed under [Secrets](https://developers.telnyx.com/docs/edge-compute/sandboxes/organization-resources/secrets.md#trust), which point common clients at `/etc/ssl/certs/ca-certificates.crt`.
2. The image's `ENV`.
3. The create's `env`.
4. Secrets delivered by `secrets_env`.
5. An exec's own `env`, for that exec.

The certificate variables are set with or without [secret rules](https://developers.telnyx.com/docs/edge-compute/sandboxes/organization-resources/secrets.md#trust).

## Reserved

| Reserved | Use |
| - | - |
| Port `49983` | Platform use. It is not reachable on a port URL. |
| `/.telnyx` | Platform files. File requests cannot write, rename, or delete under it, whether or not it exists. |
| `/run/sandbox-init/` | Platform state. |
| `TELNYX_SANDBOX_*` | Variable names reserved for the platform. None is set in the sandbox, and a create or exec `env` with the prefix is refused with `422 invalid_env`. |

## Identity

The sandbox's `/etc/machine-id` is written at its first boot. A sandbox created from a template, a snapshot, or a fork receives a new machine ID, new SSH host keys, and a reseeded random number generator before its code resumes.
