Mount Points

Mount Points

Mount points allow one container to access data stored on another node as though the files were located locally. This functionality supports data sharing between instances within the same account and can also connect containers to an external NFS server.

In this article

Mount Points Overview

A mount point creates a client-side connection to a remote directory. After the connection is established, applications inside the client container can access and work with the remote files through a local folder path.

✓

Server-side alternative

The same data-sharing relationship can also be initiated from the storage server by exporting a directory for remote access.

Mount points overview
Mount remote directories so they are accessible from another container.

Supported Protocols

NFSAvailable for all supported containers and generally recommended when transfer performance is the main requirement.
GlusterFS NativeAvailable with GlusterFS clusters and designed for concurrent access, write performance, replication and failover.

When a GlusterFS cluster is selected as the storage server, the client protocol can be chosen during mount configuration.

i

Select the protocol according to your topology

Use NFS for performance-oriented configurations. Choose GlusterFS Native when data safety, replication and storage failover are more important.

Create a Mount Point

1

Open container configuration

In the environment dashboard, click Config next to the required container or node layer.

2

Open Mount Points

In the Configuration Manager, select Mount Points from the left-side menu.

3

Click Mount

Select the Mount button to open the mount-point configuration form.

Create a new mount point
Open Mount Points in the Configuration Manager and click Mount.

Mount Operation Types

The mount form provides three connection types depending on where the shared data is stored.

Data ContainerAccesses data stored on another node within the same platform account.
Master ContainerShares one directory across all nodes of the same layer inside the current environment.
External ServerConnects the container to an NFS server located outside the platform account.
Select a mount point operation type
Choose Data Container, Master Container or External Server.

Configure Mount Settings

Common Settings

Mount PointThe local folder path where the remote content will be displayed.
Mount to All NodesCreates the same mount on every node in the layer, including nodes added later.
Read OnlyPrevents client nodes from modifying the mounted data. Read and write access is used by default.
!

Mount-point path restrictions

If the local directory does not exist, it is created automatically. The path must not begin with system directories such as /proc, /dev, /sys or /run, and it cannot replace protected paths such as /, /bin, /lib or /usr. The exact restrictions may vary by provider.

Data Container Settings

NFS ServerSelect a node from the same account that will act as the storage container.
Remote PathEnter the source directory on the remote container or choose one of its available favorite paths.
Client TypeFor GlusterFS storage, select NFS or GlusterFS Native according to your performance and resilience requirements.

Master Container Settings

NFS ServerThe master node of the selected layer is assigned automatically.
Remote PathThe same path entered in the Mount Point field is shared between the layer’s nodes.
All NodesMount to All Nodes is enabled automatically for this connection type.

External Server Settings

NFS ServerEnter the external storage server’s public IP address or custom domain name.
Remote PathEnter the path of the directory exported by the external NFS server.
1

Select the mount type

Choose the connection type that matches the storage location.

2

Enter the local and remote paths

Specify where the files should appear locally and where they are stored on the selected server.

3

Configure access options

Enable mounting for all nodes or read-only access where required.

4

Click Add

Save the configuration and allow the platform to create the mount point.

Configure mount point details
Enter the mount paths, server information and access settings.
i

First-time NFS setup may take longer

When a regular container is selected instead of a dedicated shared-storage container, the first connection may be delayed for several minutes while the required NFS software is installed.

Manage Existing Mounts

After creation, the mount point appears in the Mount Points list for the selected container or layer.

Navigate to DirectoryDouble-click the mount record to open the mounted folder and view the remote content.
Switch NodesUse the node selector in the Configuration Manager to review the mount on individual nodes.
UnmountRemove the connection when remote storage is no longer needed.
Manage existing mount points
Navigate to a mounted directory or unmount an existing connection.

Configure Write Permissions

When a mount is configured with read and write access, the source directory must allow the client container’s operating-system user to modify its files.

Connect to the storage server through SSH and adjust the directory ownership when necessary.

chown {uid}:{gid} {path}
{uid}The user identifier, which can be found in the server’s /etc/passwd file.
{gid}The group identifier, which can be checked in the /etc/group file.
{path}The remote directory or file whose ownership should be updated.
!

Apply permissions carefully

Use the correct application user and group rather than granting unrestricted access. Default usernames can differ between container images and server types.

Expected Result

The remote directory becomes available at the selected local mount point. Depending on the configuration, the files can be accessed by one node or every node in the layer, with either read-only or read-and-write permissions.

Important Notes

  • Choose NFS or GlusterFS Native according to performance and resilience requirements.
  • Do not use protected system directories as mount-point paths.
  • Enable Mount to All Nodes when the application is horizontally scaled.
  • Use read-only access when client nodes do not need to modify shared files.
  • Confirm that the remote server exports the required directory.
  • Grant appropriate ownership and permissions for read-and-write mounts.
  • Unmount unused connections before deleting or reconfiguring the storage server.

Common Issues and Solutions

Mount cannot be createdVerify the selected server, remote path, protocol and account permissions.
Local path is rejectedUse a non-protected application directory rather than a system path such as /proc, /dev or /usr.
Mounted directory is emptyConfirm that the remote path is correct and exported from the storage server.
Files cannot be editedDisable Read Only and update ownership or write permissions on the source directory.
Mount exists on only one nodeEnable Mount to All Nodes and recreate or update the mount for the entire layer.
First mount takes several minutesAllow the platform to complete the one-time NFS package installation on the selected storage node.
External server does not connectCheck its public IP or domain, NFS export settings, firewall rules and network accessibility.

Related Guides