This article describes building an image (from SQL Server full backups and applying SQL Server transaction log backups to keep it current with production and delivering database clones and containers from the image. This is useful when your database sizes are very large (usually more than 1TB). There is a working sample in windocks\samples\testIncrementalRefreshWithTransactionLogBackups. The steps are to do Gather backups, do global configuration, build the image (one time operation) and then deliver containers with database clones on an ongoing basis on demand.
Put the full backup files for your databases in a directory on the Windocks server or on a network share. A full backup is used only once. If the backups or dumps are on a network share, provide full permissions for the Windocks machine name to read and write from BOTH the network share AND the directory. For example if your Windocks machine name is PC1, then provide permissions to the account PC1$. In Computer management / Network shares, find the network share on which the backup lives and provide permissions to PC1$. Also in File Explorer, provide full permissions on the highest parent directory to PC1$. The Windocks service runs as LOCALSYSTEM, do not change that.
Designate a directory that will hold the transaction log backups on an ongoing basis as they are copied from production. Apply the same permissions as above. You may use the same directory as above for transaction log backups. This directory may be on a network share as well.