Overview
Mounts allow you to share files or directories from the host system into server containers. They can be assigned to specific eggs, nodes, or individual servers.Endpoints
List Mounts
mounts:read permission
Query Parameters:
view(optional): Set tooptionsfor a simplified list of ID and name only
Create Mount
name(required): Mount name (1-255 characters, trimmed)description(optional): Description (max 500 characters, trimmed)source(required): Host path (trimmed, minimum 1 character)target(required): Container path (trimmed, minimum 1 character)readOnly(optional): Whether mount is read-only (default: false)userMountable(optional): Whether users can mount this (default: false)nodeIds(optional): Array of node UUIDs to assign mount toeggIds(optional): Array of egg UUIDs to assign mount to
Update Mount
Delete Mount
Mount Object
Mount UUID
Mount UUID
Mount name
Mount description
Path on the host system
Path inside the container
Whether the mount is read-only
Whether users can mount this themselves
ISO 8601 timestamp
ISO 8601 timestamp
Number of eggs using this mount (list endpoint only)
Number of nodes with this mount (list endpoint only)
Number of servers using this mount (list endpoint only)
Mount Assignment
Mounts can be assigned to:- Eggs: Mount automatically applies to all servers using that egg
- Nodes: Mount is only available on specific nodes
- Servers: Mount can be individually assigned to servers
Security Considerations
- Use
readOnly: truewhen servers should not modify shared data - Carefully control
userMountableto prevent security issues - Ensure source paths exist on all assigned nodes
- Be cautious with sensitive directories (e.g.,
/etc, system paths)
Notes
- Mounts are ordered alphabetically by name
- Counts are computed via SQL joins in the list endpoint
- Use
view=optionsfor dropdown/select inputs - Audit logs track all mount operations