Member Junction
    Preparing search index...

    Runtime knobs a provider honours when provisioning.

    interface SandboxConfig {
        Concurrency?: "queue" | "fail" | "fork";
        Cpus?: number;
        DropCapabilities?: boolean;
        Image?: string;
        MemoryMb?: number;
        NetworkPolicy: HarnessNetworkPolicy;
        PidsLimit?: number;
        ReadOnlyRoot?: boolean;
        ShmSizeMb?: number;
        User?: string;
    }
    Index

    Properties

    Concurrency?: "queue" | "fail" | "fork"

    How to handle two runs wanting the same durable workspace.

    Cpus?: number

    CPU quota in cores (--cpus <n>) for container providers. Ignored by the local provider.

    DropCapabilities?: boolean

    Drop all Linux capabilities and forbid privilege escalation (--cap-drop ALL --security-opt no-new-privileges). Ignored by the local provider.

    Image?: string

    Container image, for providers that have one. Ignored by the local provider.

    MemoryMb?: number

    Hard memory limit in megabytes (--memory <n>m) for container providers. Ignored by the local provider.

    NetworkPolicy: HarnessNetworkPolicy
    PidsLimit?: number

    Maximum number of processes/threads (--pids-limit <n>) inside the container. Ignored by the local provider.

    ReadOnlyRoot?: boolean

    Mount the container's root filesystem read-only with a writable /tmp tmpfs (--read-only --tmpfs /tmp:rw,size=256m). Ignored by the local provider.

    ShmSizeMb?: number

    Size of /dev/shm in megabytes (--shm-size <n>m) for container providers (required by Chromium). Ignored by the local provider.

    User?: string

    UID/GID (--user <uid:gid>) to run container processes as so bind-mounted files match host ownership. Ignored by the local provider.