Hi everyone, I don't seem to understand the cause of different behaviour of Proxmox container mountpoints, depending on where I create them.
Pretty new to proxmox, although have considerable experience with nix systems.
I have two storage "locations" for test purposes:
1. Is a directory type, created in Datacenter > Storage, path /spinpool/shares
2. is a ZFS on zpool directly on a hard drive

I created a container, and added additional mountpoint to it. Now something happens that I don't understand.
I created them both same, however:

1. mountpoint created on my "directory" location is a .raw (image?) drive
2. mountpoint created on my spinpool is a zfs (I think?) and it's mounted and "browsable" from the point of proxmox console.
Why and what is happening? What a the implications security or performance wise?
Pretty new to proxmox, although have considerable experience with nix systems.
I have two storage "locations" for test purposes:
1. Is a directory type, created in Datacenter > Storage, path /spinpool/shares
2. is a ZFS on zpool directly on a hard drive

I created a container, and added additional mountpoint to it. Now something happens that I don't understand.
I created them both same, however:

1. mountpoint created on my "directory" location is a .raw (image?) drive
2. mountpoint created on my spinpool is a zfs (I think?) and it's mounted and "browsable" from the point of proxmox console.
Code:
root@proxmox:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
...
spinpool/subvol-110-disk-0 96K 1024G 96K /spinpool/subvol-110-disk-0
root@proxmox:~# ll /spinpool/
total 1
drwxr-xr-x 5 root root 5 Mar 12 19:10 shares
drwxr-xr-x 2 root root 2 Apr 19 10:21 subvol-110-disk-0
root@proxmox:~# ll /spinpool/subvol-110-disk-0/
total 0
root@proxmox:~# ll /spinpool/shares/images/110/
total 7235003557
-rw-r----- 1 root root 15032385536000 Apr 19 10:32 vm-110-disk-0.raw
-rw-r----- 1 root root 1099511627776 Apr 19 10:32 vm-110-disk-1.raw
Why and what is happening? What a the implications security or performance wise?