Volumes (Disks)
Learn how to map folders from your operating system into RoqueOS Server, making them appear as real disks in the web desktop's File Manager.
How it Works?
RoqueOS Server runs inside an isolated Docker container. For security reasons, it does not have automatic access to the files on your computer or host server.
In order for the File Manager to view, edit, and organize your downloads, documents, or media folders, you need to "mount" these volumes in Docker — just like plugging in a USB drive.

How to Configure
Modify the docker-compose.yml file by adding lines in the volumes: section.
Syntax:
Path-on-Your-Computer : /app/disks/DiskNameIMPORTANT RULE
The path on the right (inside RoqueOS) must always start with /app/disks/ for the File Manager to detect the folder and display it as a disk.
Practical Examples
# Linux/macOS
volumes:
- /home/user/Documents:/app/disks/Documents
# Windows
volumes:
- C:\Users\user\Documents:/app/disks/Documents# Linux/macOS
volumes:
- /mnt/external-hd/PlexMedia:/app/disks/Media
# Windows
volumes:
- D:\PlexMedia:/app/disks/Media# Linux/macOS
volumes:
- /home/user/Downloads:/app/disks/Downloads
# Windows
volumes:
- C:\Users\user\Downloads:/app/disks/DownloadsFull docker-compose.yml Example
version: '3.8'
services:
roqueos-server:
image: roqueribeiro1988/roqueos-server:latest
container_name: roqueos-server
restart: unless-stopped
ports:
- '27021:27021'
volumes:
- ./data:/app/data
- /var/run/docker.sock:/var/run/docker.sock
# Your custom disks:
- /mnt/external-hd/Movies:/app/disks/Movies
- /home/user/Downloads:/app/disks/Downloads
- /home/user/Projects:/app/disks/Projects
environment:
- TZ=America/Sao_PauloAfter Configuring
Restart the Server
Every time you change the docker-compose.yml adding or removing a volume, you need to recreate the container:
docker compose down && docker compose up -dVerify Disks on Frontend
Once the server restarts, open the File Manager in RoqueOS. You will see new virtual disk drives appear in the left pane, with the exact name you chose in /app/disks/NAME.
Common Issues
"Access Denied" error when editing files
If you get a permission error when trying to create or delete files inside a mapped disk, the Docker container does not have permission to write to the local folder. In the host server terminal:
# Read and write permission for the owner
chmod -R 755 /path/to/your/local/folder
# If you need full access (be careful)
chmod -R 777 /path/to/your/local/folderDisk doesn't appear in the File Manager
Check if:
- The path inside the container starts with
/app/disks/ - The container was restarted after the compose change
- The host path exists and has read permissions