Skip to main content
This page covers removing each Archil tool: Removing the client works the same way on Linux and macOS:
  1. Unmount every Archil disk. A clean unmount flushes recently written data to Archil and releases any files you have checked out. If you remove the client while a disk is still mounted, writes that haven’t been flushed yet are lost.
  2. Remove the software.
  3. Optionally remove local files. These include saved credentials, so remove them if the machine is being decommissioned or handed to someone else.
Uninstalling the client doesn’t change your disks or the data on them. Disks stay in your account until you delete them from the Archil console.

​
Linux

The Linux client is distributed as a package named archil. It installs two files:
1

Unmount every disk

List the Archil disks currently mounted on the server:
Unmount each one with archil unmount, which flushes pending writes before it disconnects:
Then confirm that no client processes are still running:
If a process is still listed, it’s still flushing data. Wait for it to exit, and don’t kill -9 it.
2

Remove automatic mounts

If you mount disks automatically on startup, remove the Archil entries from /etc/fstab. Otherwise, the server tries to mount them at the next boot and fails.
Also remove any startup scripts, systemd units, or configuration management that runs archil mount.
3

Remove the package

The FUSE library that the installer pulled in (libfuse2, fuse-libs, or fuse) is left installed, because other software may depend on it.
4

Remove leftover files (optional)

The package manager doesn’t remove the files below, even with apt purge, because the package didn’t create them.
To confirm that the client is gone, run the following command. It should print nothing:

​
macOS

The macOS client is a menu bar app. The first time it launches, it asks for your administrator password and installs a mount helper and a sudoers rule, so that mounting and unmounting disks doesn’t require a password. Removing the app from /Applications doesn’t remove these files, so the steps below remove them separately.
1

Unmount every disk and quit Archil

Click the Archil icon in the menu bar and choose Quit. Quitting unmounts every disk and waits for pending writes to flush.To check for any disks that are still mounted, run:
Unmount anything listed with sudo umount "/Volumes/<disk-name>".
2

Remove the app

Unregister the file system extension, then delete the app:
3

Remove the mount helper and sudoers rule

Remove the sudoers rule first, then the helper it points to:
Don’t skip this step. The sudoers rule lets administrators run /usr/local/bin/archil-mount as root without a password. Remove the rule even if the helper file is already gone.
4

Remove your data (optional)

These folders hold your Archil sign-in session, the tokens for disks you’ve mounted, and the app’s settings and caches. Run the following as each macOS user who used Archil:
If macOS denies access to the Containers or Group Containers folders, give Terminal Full Disk Access in System Settings → Privacy & Security, or delete the folders from Finder.
The disk CLI stores its profiles in ~/Library/Application Support/Archil/disk, so the first command above removes those too. To keep them, delete only the files directly inside ~/Library/Application Support/Archil and leave the disk folder in place.
To confirm that the client is gone, open System Settings → General → Login Items & Extensions → File System Extensions. Archil should no longer be listed. If it still appears, log out and log back in.
Deleting local files doesn’t revoke the credentials on Archil’s side. If the machine was lost or is moving to someone else, also remove its disk tokens from each disk’s users in the Archil console or with the Remove Disk User API.

​
disk npm package

The disk package provides two commands, disk and sandbox. It doesn’t install anything outside npm, so how you remove it depends on how you added it.
1

Remove the package

If you only run npx disk, there’s no install to remove. npx keeps a copy in npm’s cache, which npm manages on its own.
2

Delete saved profiles

If you saved credentials with disk profile create, they stay on disk after you remove the package. List your profiles, then delete each one together with its stored API key:
Or delete the whole configuration directory:If you set ARCHIL_DISK_CONFIG_DIR, profiles are stored in that directory instead.
Deleting a profile only removes the local copy of its API key. To revoke the key itself, delete it in the Archil console.

​
Kubernetes

The CSI driver runs its own copy of the client inside your cluster, so the server steps above don’t apply. First delete the pods and PersistentVolumeClaims that use Archil volumes. Then uninstall the Helm release: