Hello,
I'm running TrueNAS Scale and I created a ZFS dataset for ISO files. I created both an SMB and NFS share pointing to it so I can use those ISO's between all my Windows and Linux clients.
The share path was /mnt/pve/truenas-iso and I noticed Proxmox couldn't see the ISO's I had placed there. As I saw in other forum posts, it was because Proxmox created subdirectory /template/iso and was looking there for the .iso files - as documented here:
https://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_directory
I did not like that behavior so I'm showing you how to make Proxmox read from the root of that share rather than creating subdirectories. Yes, the documentation states you can customize the path, but it did not show an example to use the root, which may not be obvious to other Linux noobs like me.
Modify the /etc/pve/storage.cfg by adding in the line content-dirs iso=./
Example storage.cfg:
I haven't tested it but I assume you can do the same for the other content types.
I'm running TrueNAS Scale and I created a ZFS dataset for ISO files. I created both an SMB and NFS share pointing to it so I can use those ISO's between all my Windows and Linux clients.
The share path was /mnt/pve/truenas-iso and I noticed Proxmox couldn't see the ISO's I had placed there. As I saw in other forum posts, it was because Proxmox created subdirectory /template/iso and was looking there for the .iso files - as documented here:
https://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_directory
I did not like that behavior so I'm showing you how to make Proxmox read from the root of that share rather than creating subdirectories. Yes, the documentation states you can customize the path, but it did not show an example to use the root, which may not be obvious to other Linux noobs like me.
Modify the /etc/pve/storage.cfg by adding in the line content-dirs iso=./
Example storage.cfg:
Code:
nfs: truenas-iso
export /mnt/rust/iso
path /mnt/pve/truenas-iso
server 192.168.10.100
content iso
options vers=4.2,soft
content-dirs iso=./I haven't tested it but I assume you can do the same for the other content types.
