Mounts
Persist data and inject files into your services with volume, bind, and file mounts.
Containers are ephemeral — anything written inside them is lost on redeploy. Mounts let you persist data and provide configuration files to your services. They are available for applications, Docker Compose services, and every database type (PostgreSQL, MySQL, MariaDB, MongoDB, Redis).
Mount types
Skitflow supports three mount types, each with its own fields:
- Volume — a named Docker volume managed by Skitflow. Provide a Volume Name and the Mount Path inside the container. Best for persistent application data (uploads, database files).
- Bind — mounts a path from the host server into the container. Provide a Host Path and the Mount Path. Use this when you need to share a specific directory from the server.
- File — creates a file from inline Content and mounts it at the given Mount Path. Ideal for config files, certificates, or secrets that should live next to your app.
| Type | Required fields |
|---|---|
| Volume | Volume Name, Mount Path |
| Bind | Host Path, Mount Path |
| File | Content, Mount Path |
The Mount Path is the location inside the container (for example /app/data or /etc/myapp/config.yml). Named volumes are the recommended option for data that must survive redeploys.
Managing mounts
Add as many mounts as a service needs and update or remove them at any time. Mount changes are applied when the service is redeployed.
Removing a volume mount does not automatically delete the underlying volume data. Bind mounts depend on the host path existing on the target server.