BYOH storage and resource limits

Open My hardware → your server → Storage. The agent reports Docker’s default storage and detected mounted filesystems.

Add storage

You configure and mount additional disks in the host operating system. The panel does not format, partition or mount them. Verify the mount is persistent across reboots before using it for app data.

The Storage page marks which filesystems are eligible for app deployment and explains unavailable choices. If eligible, use Deploy app here or choose that storage location during deployment.

What does not move

Choosing storage for a new app does not move existing apps, Docker images or container layers. The Docker default location still needs free space. Moving or unmounting a filesystem containing app data can break those apps.

Monitor limits and usage

BYOH CPU and memory limits are ceilings rather than reserved capacity, and overcommit is allowed. Disk is shared without per-app space reservations in this workflow. An unlimited limit does not create more hardware capacity.

Watch actual usage and free space. A full filesystem can affect every app using it. If the server is offline, displayed storage information may be the last reported state.

This storage picker is not a general S3 mount service. App-native S3 settings, network filesystems and local block storage have different behavior; confirm the app and storage requirements before changing them.