The shared drive

One shared drive per account, always there. Attach it anywhere; every machine sees the same files at the same path, at the same time.

What it is

The shared drive is a single volume per account. It is always there at a fixed 10 GiB; there is nothing to create, size, or delete. Attach it to the machines that need it; each mounts it at /mnt/share and all read and write the same files simultaneously. Machines without it attached don't see it at all. Put build artifacts, datasets, anything several machines share there.

Your drive

Check the drive's size and where it's attached any time:

ssh

$ ssh dashboard@ironwire.sh drive
drive: 10 GiB — attached to app, worker (mounts at /mnt/share)

dashboard

Press d to open the drive panel; the machine list's DRIVE column also shows attached on every machine that mounts it.

Attaching and detaching

Attach at machine creation with --drive:

$ ssh dashboard@ironwire.sh create worker --drive
created worker
  url: https://worker-alice.ironwire.xyz
  ssh: ...

On an existing machine, use drive attach. It takes effect on the next boot. Restart the machine to pick up the change.

ssh

$ ssh dashboard@ironwire.sh drive attach app
drive attached to app (takes effect on next boot)
$ ssh dashboard@ironwire.sh restart app
restarted app

dashboard

Press d to open the drive panel (a list of your machines), select one and press ↵ to toggle its mount. Restart the machine with r from the machine list to apply.

After the reboot, the drive is at /mnt/share inside the guest. Detaching works the same way, also on the next boot:

ssh

$ ssh dashboard@ironwire.sh drive detach app
drive detached from app (takes effect on next boot)

dashboard

Press d, select an attached machine, and press ↵ to toggle the mount off.

note Detaching from every machine leaves the drive and its files in place; nothing is deleted. The next machine you attach sees the same files.

Capacity and your storage pool

The drive counts against your account's storage pool by what it actually holds: measured data, alongside what your machines store, not its 10 GiB ceiling. That ceiling caps how much the shared drive could hold, so a runaway write on one machine can't consume your whole pool through it. Deleting files inside the drive frees pool room. Check where you stand with usage; see Quotas for how the pool works.