Volumes

Volumes provide persistent storage for your game servers. Without volumes, all data inside a container is lost when the server is stopped.

How Volumes Work

Each volume mount maps a path inside the container to a directory on the host machine. When the game server writes files to the mounted path, those files are actually stored on the host — outside the container.

Host: /opt/cosy/volumes/<volume-mount-uuid>
        ↕ (mounted)
Container: /data

The host-side path is managed entirely by COSY — each volume mount gets an internal UUID that isn't visible in the UI. You don't need to know or interact with this path directly. Instead, use the File Browser to access your server files.

Configuring Volume Mounts

In the Settings view, you can add volume mounts by specifying:

COSY automatically manages the host-side path. Each volume mount is stored under the COSY volumes directory (default: /opt/cosy/volumes) with an auto-generated UUID as the directory name.

Data Lifecycle

• Server start — Volumes are mounted into the new container
• Server stop — Container is removed, volumes remain on disk
• Server restart — New container mounts the same volumes, data is preserved
• Server delete — Volumes are cleaned up along with the server

Accessing Volume Files

You can browse and edit files in your volumes through the File Browser in the COSY web interface.