Difference between revisions of "UnRAID tips"
| Line 7: | Line 7: | ||
== 5.25" to 5X 3.5" Hard Drive Tray == | == 5.25" to 5X 3.5" Hard Drive Tray == | ||
| − | * "Cons: Not compatible with WD Red series HDD because of a design flaw." <ref>https://www.newegg.ca/Product/SingleProductReview.aspx?ReviewID=5119635</ref> | + | * ORICO 1106SS-V1-BK |
| + | ** "Cons: Not compatible with WD Red series HDD because of a design flaw." <ref>https://www.newegg.ca/Product/SingleProductReview.aspx?ReviewID=5119635</ref> | ||
== References == | == References == | ||
<references /> | <references /> | ||
Revision as of 17:33, 13 January 2019
host volume paths and the container paths
- "The host path is (generally) your shares that you want to give the container access to. Best practice for containers dictates that if the container only needs access to a Downloads share, that you only create a mapping for the Downloads share."
- eg. /mnt/user/Downloads
- "On the container path side of things, you tell the container how it should "refer" to the host path. IE: If the container path is /Downloads, then whenever you tell the container to save something into /Downloads, docker will then "map" it and actually store it on your unRaid system at /mnt/user/Downloads." [1]
5.25" to 5X 3.5" Hard Drive Tray
- ORICO 1106SS-V1-BK
- "Cons: Not compatible with WD Red series HDD because of a design flaw." [2]
