Mounts is a feature that allows administrators to mount other directories from the host file-system into a Server's container.
For security reasons it is not possible to mount directories on a node by default. Directories that should be mountable have to be specified explicitly in the Wings configuration.
In the Wings configuration file (
allowed_mounts field is used to list mountable directories. The listed directories and all their subdirectories can be mounted.
allowed_mounts: - /example
You have to restart Wings to apply new changes to your Wings config.
You have to configure mounts in admin Panel in order to use them with your servers. They consist of a source pad on the node and a target path where it will be mounted in the container.
Path in the container
Mounts cannot be mounted to or inside of
/home/container or any subdirectory of it, nor can you cross-mount servers such as Server A's directory into Server B.
/home/containerin the path.
Mounts used by multiple servers
All servers using the same mounts will only share their contents when they are on the same node. Mounts are not synchronized between nodes.
The files of the mount should become available in the target path in the container. You can temporarily change your server startup command to
ls <mount target>, which should output the contents of the mount if configured correctly.
Mounts cannot be accessed
Mounts do not appear in the Panel's file manager, nor are they accessible via SFTP. However, the server itself will be able to see and use the mounts.
The example mount below is stored in the path
/var/lib/pterodactyl/mounts, which we add to the Wings
allowed_mounts: - /var/lib/pterodactyl/mounts