# AIStor Memory (aimem) RELEASE.2026-10-30T22-40-52Z

Released: 2026-10-30

This AIStor Memory (aimem) release fixes Kubernetes volumes on a Memory Bucket named after an `aimem` command, such as
`list` or `delete`, which failed to mount with the CSI driver from RELEASE.2026-10-30T18-15-12Z. The documentation and
`aimem --help` now recommend giving the bucket as an `s3://bucket/` URI.

---

## Downloads

### Binaries

| Platform | Architecture | Download                                                                                                                            |
| -------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| Linux    | amd64        | [aimem.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem.RELEASE.2026-10-30T22-40-52Z) |
| Linux    | arm64        | [aimem.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem.RELEASE.2026-10-30T22-40-52Z) |

The setuid `aimem-fusermount` mount helper, the `aimem-bio` binary that `aimem bio` runs, and the Kubernetes CSI node
driver are published beside it:

| Binary             | Architecture | Download                                                                                                                                                  |
| ------------------ | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `aimem-fusermount` | amd64        | [aimem-fusermount.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-fusermount.RELEASE.2026-10-30T22-40-52Z) |
| `aimem-fusermount` | arm64        | [aimem-fusermount.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-fusermount.RELEASE.2026-10-30T22-40-52Z) |
| `aimem-bio`        | amd64        | [aimem-bio.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-bio.RELEASE.2026-10-30T22-40-52Z)               |
| `aimem-bio`        | arm64        | [aimem-bio.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-bio.RELEASE.2026-10-30T22-40-52Z)               |
| `aimem-csi-driver` | amd64        | [aimem-csi-driver.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-csi-driver.RELEASE.2026-10-30T22-40-52Z) |
| `aimem-csi-driver` | arm64        | [aimem-csi-driver.RELEASE.2026-10-30T22-40-52Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-csi-driver.RELEASE.2026-10-30T22-40-52Z) |

Each binary has `.sha256sum`, `.minisig`, and `.asc` files at the same path. These links point into `archive/`, where a
release's files stay after a newer release ships, so they always serve this build. The unversioned
`…/linux-{arch}/aimem` path serves whatever release is newest.

### Packages

`.deb`, `.rpm`, and `.apk` install the `aimem` client, the setuid `aimem-fusermount` mount helper
(`/usr/bin/aimem-fusermount`, mode 4755), and `aimem-bio`. They also install a disabled example `mnt-aimem.mount`
systemd unit and the `/sbin/mount.aimem` helper it needs.

| Format | Architecture | Download                                                                                                                                    |
| ------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| DEB    | amd64        | [aimem_20261030224052.0.0_amd64.deb](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem_20261030224052.0.0_amd64.deb)         |
| DEB    | arm64        | [aimem_20261030224052.0.0_arm64.deb](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem_20261030224052.0.0_arm64.deb)         |
| RPM    | amd64        | [aimem-20261030224052.0.0-1.x86_64.rpm](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-20261030224052.0.0-1.x86_64.rpm)   |
| RPM    | arm64        | [aimem-20261030224052.0.0-1.aarch64.rpm](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-20261030224052.0.0-1.aarch64.rpm) |
| APK    | amd64        | [aimem_20261030224052.0.0_x86_64.apk](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem_20261030224052.0.0_x86_64.apk)       |
| APK    | arm64        | [aimem_20261030224052.0.0_aarch64.apk](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem_20261030224052.0.0_aarch64.apk)     |

The packages depend only on libc (`libc-bin` / `glibc-common`); no `libfuse` is needed.

### Container Images

```bash
# The aimem client, pinned to this release:
docker pull quay.io/minio/aistor/aimem:RELEASE.2026-10-30T22-40-52Z

# The Kubernetes CSI node driver, pinned to this release:
docker pull quay.io/minio/aistor/aimem-csi-driver:RELEASE.2026-10-30T22-40-52Z
```

The `latest` tag of each image also points at this release, but moves when the next one ships. To verify a build, pin
the release tag or a `@sha256:` digest, never `latest`.

Mounting from a container needs `/dev/fuse`. As root, it also needs `CAP_SYS_ADMIN` (or `--privileged`). As a non-root
user, the container needs `SYS_ADMIN` added to its capabilities and `allowPrivilegeEscalation: true`, so the setuid
helper can run.

### Verification

Each binary is signed with minisign (preferred) and GPG, and has a sha256sum file.

```bash
BASE=https://dl.min.io/aistor/aimem/release/linux-amd64/archive
curl -fsSLO $BASE/aimem.RELEASE.2026-10-30T22-40-52Z
curl -fsSLO $BASE/aimem.RELEASE.2026-10-30T22-40-52Z.minisig
curl -fsSLO $BASE/aimem.RELEASE.2026-10-30T22-40-52Z.sha256sum

# minisign
minisign -Vm aimem.RELEASE.2026-10-30T22-40-52Z \
  -P RWTx5Zr1tiHQLwG9keckT0c45M3AGeHD6IvimQHpyRywVWGbP1aVSGav

# sha256: the checksum file names the versioned binary, so keep that file name
sha256sum -c aimem.RELEASE.2026-10-30T22-40-52Z.sha256sum
```

The minisign public key above is the MinIO release-signing key, used across the AIStor product line.

---

## Changes since RELEASE.2026-10-30T18-15-12Z

### Bug Fixes

#### Kubernetes CSI driver

- A volume whose bucket is named `create`, `convert`, `list`, `get`, `delete` or `credentials`, and that sets no
  `prefix`, failed to mount with the RELEASE.2026-10-30T18-15-12Z driver, because `aimem` ran the command of that name
  instead. The driver now passes every bucket to `aimem` as an `s3://` URI, so these volumes mount again with no change
  to their attributes. (#272)

### Documentation

- The mount examples, the CLI reference and `aimem --help` now give the bucket as `s3://bucket/`, or
  `s3://bucket/prefix/` for a sub-prefix. A URI is never taken for an `aimem` command, so use it in scripts, fstab
  entries and systemd units. The bare `bucket` and `bucket/prefix/` forms still work. (#272)

### Platform / Compatibility

- Linux amd64 and arm64, glibc 2.34 or later.
- Mounting needs `/dev/fuse`. As root, or with `CAP_SYS_ADMIN`, aimem mounts directly; any other user mounts through the
  setuid `aimem-fusermount` helper. FUSE passthrough also needs `CAP_SYS_ADMIN`; without it, a mount serves ordinary
  FUSE reads.

---

## Security & Compliance

Software bills of materials (SBOMs) for this release, generated from the `Cargo.lock` files at the release tag. The
dependencies are unchanged from RELEASE.2026-10-30T18-15-12Z.

| Component          | SPDX                                                                                                                                              | CycloneDX                                                                                                                                       |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `aimem`            | [aimem-RELEASE.2026-10-30T22-40-52Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-10-30T22-40-52Z.spdx.json)         | [aimem-RELEASE.2026-10-30T22-40-52Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-10-30T22-40-52Z.cdx.json)         |
| `aimem-bio`        | [aimem-bio-RELEASE.2026-10-30T22-40-52Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-bio-RELEASE.2026-10-30T22-40-52Z.spdx.json) | [aimem-bio-RELEASE.2026-10-30T22-40-52Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-bio-RELEASE.2026-10-30T22-40-52Z.cdx.json) |
| `aimem-csi-driver` | [aimem-csi-RELEASE.2026-10-30T22-40-52Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-csi-RELEASE.2026-10-30T22-40-52Z.spdx.json) | [aimem-csi-RELEASE.2026-10-30T22-40-52Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-csi-RELEASE.2026-10-30T22-40-52Z.cdx.json) |

For `aimem`, also the
[crate list](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-10-30T22-40-52Z.crates.txt) and
[dependency tree](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-10-30T22-40-52Z.cargo-tree.txt).

---

## Upgrade Instructions

- **Kubernetes:** pin both image references in the DaemonSet to
  `quay.io/minio/aistor/aimem-csi-driver:RELEASE.2026-10-30T22-40-52Z`. If you held a volume's driver at
  RELEASE.2026-10-27T17-44-57Z because of the known issue in RELEASE.2026-10-30T18-15-12Z, you can upgrade it now.
- **Upgrading from a release before RELEASE.2026-10-30T18-15-12Z:** read the
  [RELEASE.2026-10-30T18-15-12Z notes](https://dl.min.io/aistor/aimem/release/notes/release-notes-RELEASE.2026-10-30T18-15-12Z.md)
  first. They reserve six bucket names for the new top-level commands and make `aimem delete` ask for confirmation.

## Documentation

- Hosted docs: <https://docs.min.io/aimem/>

## Support

- Security disclosures: security@min.io
- Licensed customers and contributors: contact MinIO support.
