I never use su, i use sudo so thats not the problem
su - didn't work any better anyway, but i can just add sbin to path manually, thats not a problem
regarding your zfs-mount problem - last couple of times we encountered this it was due to a mismatch in the zpool-cache in initramfs and on disk, which prevented the automatic mounting during boot - the following steps helped:
* set the cachefile property on each pool (this makes sure that all pools are inside): `zpool set cachefile=/etc/zfs/zpool.cache <poolname>`
(again you need to do this for rpool and zTank)
* sync the updated zpool.cache to your initramfs: `updated-initramfs -k all -u`
* reboot and check whether the problem is fixed
This didn't make any difference it seems...
But i think the problem is in how i'w messed up the network shares :-X
But since i wrote this i'w done some reaserch and messed around a lot... Seems like all this is due to me messing with everything (as usual), anyway....some backstory
I have 2 servers, this one is a hp gen8 microserver, the second one is a hp gen7 dl380, since i can't afford large 2,5" disks atm i keept the microserver to host the 4x3tb over nfs to the dl380... Both servers run proxmox in case i wanted to move some VMs over to the microserver for some reason
The 3x4tb is mounted on the dl380 as /zTank and to be able to seamlessly move stuff over between servers i mounted the same share to /zTank on the microserver.... But now it seems like the update cofused the real zTank share with the nfs one...
I managed to remove the nfs share in through the proxmox gui and add the and add the reall storage in the storage settings in the gui, now the right share is located under the node in the left frame of the gui
it's just not mounted, so thats what im currently looking in to, how to have it auto mount
usualy i just add stuff to the fstab, but i figured I'd try to fix it the right way this time around, is there a setting in tje gui for this?
for completeness sake - running docker directly on PVE is not really supported.
also I probably would not use rpool/pve-1 as root of the docker-storage in that case, but rather create a fresh dataset
Yea I'm aware
thing is this all started with a debian server running docker, then i installed proxmox on top of it. I loved the proxmox interface and decided to redo the entire server and install proxmox first and have docker in a vm.... But in the last minute I decided against WM and just had it running on the host. I will how ever look in to giving docker its on dataset
Sorry for the miss information initially, i guess i had no idea what was wrong to begin with after all ;-D
