Mount Management

​

What are Mounts?

public static array $validationRules = [
    'name' => 'required|string|min:2|max:64|unique:mounts,name',
    'description' => 'nullable|string|max:191',
    'source' => 'required|string',
    'target' => 'required|string',
    'read_only' => 'sometimes|boolean',
    'user_mountable' => 'sometimes|boolean',
];

​

Mount Properties

• Name: Unique identifier for the mount
• Description: What the mount contains
• Source: Path on the host system
• Target: Path inside the container
• Read Only: Whether users can write to the mount
• User Mountable: Whether users can mount/unmount themselves

​

Creating a Mount

​

Path Restrictions

​

Invalid Source Paths

public static $invalidSourcePaths = [
    '/etc/pterodactyl',
    '/var/lib/pterodactyl/volumes',
    '/srv/daemon-data',
];

​

Invalid Target Paths

public static $invalidTargetPaths = [
    '/home/container',
];

​

Assigning Mounts to Nodes

public function addNodes(Request $request, Mount $mount): RedirectResponse
{
    $data = $request->validate(['nodes' => 'required|exists:nodes,id']);

    $nodes = $data['nodes'] ?? [];
    if (count($nodes) > 0) {
        $mount->nodes()->attach($nodes);
    }

    $this->alert->success('Mount was updated successfully.')->flash();

    return redirect()->route('admin.mounts.view', $mount->id);
}

​

Assigning Mounts to Eggs

public function addEggs(Request $request, Mount $mount): RedirectResponse
{
    $validatedData = $request->validate([
        'eggs' => 'required|exists:eggs,id',
    ]);

    $eggs = $validatedData['eggs'] ?? [];
    if (count($eggs) > 0) {
        $mount->eggs()->attach($eggs);
    }

    $this->alert->success('Mount was updated successfully.')->flash();

    return redirect()->route('admin.mounts.view', $mount->id);
}

​

Why Assign to Eggs?

• Only relevant servers get the mount
• Better security and isolation
• Cleaner server configurations

• Map mounts only for Source Engine eggs
• Plugin directories only for Minecraft eggs
• Asset libraries only for specific game types

​

Mount Relationships

​

Eggs Relationship

public function eggs(): BelongsToMany
{
    return $this->belongsToMany(Egg::class);
}

​

Nodes Relationship

public function nodes(): BelongsToMany
{
    return $this->belongsToMany(Node::class);
}

​

Servers Relationship

public function servers(): BelongsToMany
{
    return $this->belongsToMany(Server::class);
}

​

User Mountable Option

• Users can see the mount in their server settings
• Users can toggle the mount on/off for their servers
• Useful for optional content (maps, plugins)

• Only admins can assign the mount
• Automatically mounted on applicable servers
• Users cannot remove it

​

Node Configuration

'allowed_mounts' => $this->mounts->pluck('source')->toArray(),

​

Common Use Cases

​

Shared Map Repository

Name: source-maps
Description: Shared Source Engine maps
Source: /mnt/storage/source-maps
Target: /home/container/csgo/maps
Read Only: true
User Mountable: false

• CS:GO, TF2, Garry’s Mod eggs
• All nodes hosting Source servers

​

Plugin Library

Name: minecraft-plugins
Description: Common Minecraft plugins
Source: /mnt/storage/mc-plugins
Target: /home/container/plugins-library
Read Only: true
User Mountable: true

• Paper, Spigot, Bukkit eggs
• All Minecraft nodes

​

Shared Configuration

Name: server-configs
Description: Default server configurations
Source: /mnt/storage/configs
Target: /home/container/defaults
Read Only: true
User Mountable: false

​

Mod Repository

Name: mod-library
Description: Available game mods
Source: /mnt/storage/mods
Target: /home/container/available-mods
Read Only: true
User Mountable: true

​

Security Considerations

​

Read-Only Mounts

• Prevents users from modifying shared content
• Protects against malicious file modifications
• Ensures consistency across servers

​

Path Validation

• Never mount sensitive system directories
• Avoid mounting directories with write access to critical files
• Use specific paths, not broad directories

​

User Mountable Security

• The content is safe for all users
• Read-only access is enforced
• The mount doesn’t contain sensitive data

​

Managing Existing Mounts

​

Viewing Mounts

• Mount name and description
• Source and target paths
• Number of assigned nodes
• Number of assigned eggs
• Number of servers using the mount

​

Editing a Mount

​

Removing Nodes or Eggs

1. Navigate to the mount
2. Click the X next to the node or egg
3. Confirm removal

public function deleteEgg(Mount $mount, int $egg_id): Response
{
    $mount->eggs()->detach($egg_id);
    return response('', 204);
}

public function deleteNode(Mount $mount, int $node_id): Response
{
    $mount->nodes()->detach($node_id);
    return response('', 204);
}

​

Deleting a Mount

public function delete(Mount $mount): RedirectResponse
{
    $mount->delete();

    return redirect()->route('admin.mounts');
}

​

Troubleshooting

​

Mount Not Available

1. Verify mount is assigned to the server’s egg
2. Check mount is assigned to the server’s node
3. Ensure user_mountable is enabled (if user-facing)
4. Restart Wings on the node

​

Permission Denied

1. Check source directory exists on the node
2. Verify directory permissions (should be readable by Wings)
3. Check SELinux/AppArmor policies
4. Ensure Docker can access the path

​

Files Not Syncing

1. Verify the mount is active (check server settings)
2. Restart the server container
3. Check Wings logs for mount errors
4. Ensure source path is correct

​

Best Practices

1. Use Read-Only: Default to read-only mounts for security
2. Specific Paths: Mount specific directories, not entire drives
3. Document Mounts: Clearly describe what each mount provides
4. Test First: Test mounts on a development server before production
5. Consistent Paths: Use the same source paths across all nodes
6. Regular Audits: Review mounts periodically for security
7. Backup Sources: Keep backups of important mounted directories

​

Next Steps