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

# Mount on Linux

> Install the CLI and prepare a Linux environment for FUSE mounts.

Amulet mounts run on Linux `x86_64` and `aarch64`. The host must provide FUSE
and allow the process to create a filesystem mount.

<Steps>
  <Step title="Check the environment">
    Confirm the operating system, architecture, and FUSE device:

    ```bash theme={null}
    uname -s
    uname -m
    test -c /dev/fuse && echo "FUSE is available"
    ```

    The first command must print `Linux`. If the FUSE check prints nothing, enable
    FUSE through your Linux distribution or compute provider before continuing.
  </Step>

  <Step title="Install the CLI">
    ```bash theme={null}
    curl -fsSL https://amulet.so/install.sh | sh
    ```

    For a non-root install, the binary is placed in `~/.local/bin`. Run the `PATH`
    command printed by the installer if that directory is not already available.
  </Step>

  <Step title="Export an API key">
    Create a key in the [Amulet dashboard](https://app.amulet.so/?tab=api-keys),
    copy it when it appears, and export it in the shell that will run the mount:

    ```bash theme={null}
    export AMULET_API_KEY=amulet_...
    ```
  </Step>

  <Step title="Start the mount">
    The local path can be missing or empty. Amulet creates a missing path:

    ```bash theme={null}
    amulet mount demo ./demo
    ```

    The command stays in the foreground. Keep it running and use another terminal
    or process to read and write `./demo`.
  </Step>

  <Step title="Unmount cleanly">
    ```bash theme={null}
    amulet unmount ./demo
    ```

    Wait for the mount process to exit before shutting down the host.
  </Step>
</Steps>

## Read-only mounts

Pass `--ro` when a process should not change a live volume or branch:

```bash theme={null}
amulet mount demo ./demo-readonly --ro
```

Snapshot mounts are always read-only, even without `--ro`.

## Containers and sandboxes

A container or sandbox must expose `/dev/fuse` and permit filesystem mounts.
The exact setting depends on the compute provider. Use a normal host or VM if
the environment does not allow FUSE.

See [Troubleshooting](/troubleshooting) for common mount failures.