Skip to main content
A network share is a saved record of an NFS export or a CIFS (SMB) share on your network, such as a NAS. You register it once, with the host, remote path and credentials, and test that the host answers. The record is stored by the control plane, and a CIFS password is stored encrypted with the master key, never returned by the API.
Registration only, for nowToday a network share is a managed record plus a reachability test. Nothing in the control plane yet creates a Docker volume from a share or mounts one into an app. The translation to Docker’s built-in local driver NFS and CIFS options exists in internal/docker, but no code path calls it. The dashboard page text describes attaching a share as an app volume source; treat that as the intended direction, not a shipped capability. To use a share in an app today, mount it on the node yourself and bind-mount the path with a hostPath volume.

Add a share

Open Settings, then Network shares, and add a share. Choose NFS or CIFS and fill in the fields below.
Creating a share with credentials needs the control plane’s master key to be configured. Without one, the API refuses with a “not implemented” error. An NFS share carries no credentials.

Test, update and remove

  • test opens a TCP connection from the control plane to the share’s host on the protocol’s standard port (2049 for NFS, 445 for CIFS) with a 10 second timeout. A failure returns the address it could not reach. This is a reachability check only. It does not authenticate and never reads the CIFS password, so a passing test does not prove the credentials or the export path are right.
  • update takes the full set of required fields again. Omit --password to keep the existing password; pass it to rotate it.
  • delete removes the record. The control plane’s secrets store has no delete operation yet, so a deleted CIFS share’s encrypted password stays in the store, unreferenced.
All subcommands accept the standard --token, --api-url, --profile, --json, --output and --query flags.

API

A share does not appear on the project topology graph, because no stored link ties a share to an app volume.

Next steps

Backups and storage

Backup targets and volume backups.

App spec reference

Volumes and host-directory bind mounts.
Last modified on October 12, 2026