Configuring Storage

The containers are ephemeral entity, all the data inside the container is lost when the containers are destroyed/removed. So, data must be saved to Storage Volume by using the volume. For more information see, Volumes.

Special Considerations

  • Map work, cfg, security and secure+ directories to Storage Volume

  • For data persistence, either host path or NFS mounted shared directories should be used.

    It is recommended that NFS mounted shared drive be used to map these directories.

  • Saving the configuration on Storage Volume mounted shared drive enables creating a new container using the saved configuration on a different node that can access the mapped path.

  • To send/receive files, user must map the source/destination directory path on host/NFS to inside the container mounted path of upload/download directory while running the container.
    Note: For using the hostpath with SELinux policy enforced, you need to set the proper SELinux policy label for each mounted directory. One can set it using the following command:
    chcon -Rt svirt_sandbox_file_t <Path_Of_Directory_To_Be_Mounted>