Skip to main content

​
amulet: command not found

The installer places non-root installs in ~/.local/bin. Add it to PATH, then open a new shell or run:

​
AMULET_API_KEY is required

Export the key in the same shell that runs the CLI:
If the key was revoked, create a new one in the dashboard.

​
The mount fails before it starts

Confirm that the environment is Linux and exposes the FUSE device:
Containers and managed sandboxes must explicitly allow FUSE mounts.

​
The mount directory is not empty

Amulet refuses to mount over existing files. Choose a new path or move the existing files elsewhere before mounting:

​
The mount command appears to hang

This is expected: amulet mount remains in the foreground for the lifetime of the mount. Wait for the mounted message, keep that process running, and use another terminal for file operations.

​
A snapshot mount is read-only

Snapshots are immutable. Create a writable branch from the snapshot:

​
A snapshot cannot be found

List snapshots on the same volume or branch used when it was created:
Snapshot names are resolved within that volume or branch.

​
A branch has different source information

--from and --from-snapshot apply when a branch is first created. If the target name already exists with another source, choose a new branch name or mount the existing branch without source flags.

​
Unmounting fails

Pass the exact local mount path:
If you used an absolute path to mount, use the same path when unmounting. Wait for the original mount process to exit before mounting at that path again.

​
A dashboard volume or usage value is unexpected

API keys are organization-scoped. Switch to the organization that owns the key and confirm its Volumes and Usage tabs. For command syntax, run amulet --help or see the CLI reference.