To force Proxmox to update the available template you can runpveam update. It does this daily, but it might not have done it on a fresh install, so you can force it before you select a container template.

A bind mount allows you to pass storage mounted by the node/host to a container as if it was locally mounted by it as well. A dedicated ZFS storage vault you want shared to the network is the primary use case. There are a few different ways to achieve this, but the article link below covers the recommended way. The container can then handle SMB/NFS shares in whatever way needed.

ProxMox Wiki article for Bind-Mounts

Make sure ProxMox sees the pool with zpool list.

Mount the pool with zpool import poolname. Augment with zpool import -f poolname if pool was not properly exported from original host.

The pool should be mounted at /poolname. This pool does not show up in the GUI by default. A PVE purposed store can be added to it to be utilized by the system.

nano /etc/ssh/sshd_config

Uncomment PermitRootLogin and change value to yes.

Save and restart ssh service systemctl restart ssh

I you need to change the IP of the PVE Node after setting it up on a different network you need to manually set it via CLI. With physical command line access, change the IP address in the following 2 locations:

nano /etc/network/interfaces

nano /etc/hosts