Overview
You can use persistent storage to expand the overall storage space for newly created containers. You can use this storage to store logs or any other miscellaneous content.
After you add persistent storage, you can use this document to learn:
- How to locate persistent storage volume
- Tips before you edit or delete a workload with persistent storage
You can only add persistent storage when you first create a new workload; you cannot add persistent storage to an existing workload.
- To learn how to create a workload with persistent storage, see Create and Manage Virtual Machines, Containers, and Workloads.
Locate the persistent storage volume
When you use SSH to connect to your workload, you can navigate to the storage location in the directory that you specified when you first created the workload.
For example, if the storage was mounted in /mnt/example
, then you can verify the existence of the mount using the df-h
command on any virtual machine-based workload or Linux-based container.
In the following table, the bolded line shows the persistent storage location:
Filesystem | Size | Used | Avail | Use% |
Mounted on |
udev | 985M | 0 | 985M | 0% | /dev |
tmpfs | 200M | 3.0M | 197M | 2% | /run |
/dev/vda1 | 20G | 1.4G | 18G | 8% |
/ |
tmpfs | 998M | 0 | 998M | 0% | /dev/shm |
tmpfs | 5.0M | 0 | 5.0M | 0% | /run/lock |
tmpfs | 998M | 0 | 998M | 0% | /sys/fs/cgroup |
/dev/vdb | 24G | 45M | 23G | 1% | /mnt/example |
tmpfs | 200M | 0 | 200M | 0% | /run/user/1000 |
Edit or delete a workload
Before you edit or delete a workload, consider the following statements:
Edit a workload | Delete a workload |
|
|