Operations

Support and compatibility

This page explains how to reach us. It describes how mountOS handles versioning and releases. It also describes what compatibility to expect when you integrate with mountOS or upgrade it.

support@mountos.io

Web

mountos.io

Downloads

mountos.sh/install

Versioning

mountOS follows semantic versioning, MAJOR.MINOR.PATCH. The build process compiles the version into every binary. Each binary reports its version at runtime. mountOS is in the 0.x series, before its 1.0 release. During the 0.x series, a minor version bump can include breaking changes. Read the release notes before you upgrade to a new minor version. Pin an exact version or a major series for reproducible deployments.

Bump	Example	Meaning
patch	`0.1.0` to `0.1.1`	Backward-compatible fixes
minor	`0.1.1` to `0.2.0`	Backward-compatible additions (can break compatibility in the 0.x series)
major	`0.2.0` to `1.0.0`	Breaking changes

Platform and architecture support

Component	Platforms
Server services (appserv, dataserv, blockserv, gcserv)	Linux only, amd64 and arm64
Client CLI (`mountos`), including the S3 and WebHDFS surfaces	Linux (amd64, arm64), macOS (universal), Windows (amd64, arm64)
Kubernetes CSI node driver (`mountos kubernetes`)	Linux only, amd64 and arm64
macOS app bundle (`mountos-macos`)	macOS universal
Windows app and driver (`mountos-windows`)	Windows amd64

mountOS code-signs macOS client binaries with a Developer ID identity. mountOS also notarizes them for Gatekeeper. mountOS signs Windows client binaries with an Authenticode signature. mountOS timestamps them with RFC 3161.

API compatibility

Third parties integrate through the client's standards-compatible protocol surfaces. Start both with mountos gateway --gateway s3,hdfs. You can also pass --gateway to mountos mount.

S3: an Amazon S3-compatible API that accepts an S3-compatible request signature. Standard S3 tooling such as the AWS CLI and boto3 interoperates. ListObjects and ListObjectsV2 clamp max-keys to the AWS ceiling of 1000. Multipart uploads follow S3 conventions. Every part except the last must be at least 8 MiB. Part numbers run from 1 to 10000.
WebHDFS: the WebHDFS REST API for Hadoop-ecosystem clients. mountOS serves it under /webhdfs/v1. Requests authenticate with an S3-compatible request signature that uses the service name hdfs. Defaults follow Hadoop conventions. mountOS advertises a 128 MiB block size and a replication factor of 1 by default. mountOS replicates data on the server. This replication factor value is informational only.

Protocol compatibility

Server components support rolling upgrades within the compatibility range stated in the release notes.

Upgrade guidance

Pin an exact version (--version X.Y.Z) for reproducible deployments. Alternatively, pin a major series (--major N) to receive compatible updates.
The installer verifies the published SHA-256 automatically. If you download an artifact from another source, you must check it against the published .sha256 file or the manifest checksum.
Plan rolling upgrades so that no node advertises a protocol version outside the accepted window.
During the 0.x series, treat every minor version bump as a possible breaking change. Read the release notes first.

For anything not covered here, contact support@mountos.io.