I have been trying to setup the Emby App. Initially I made a mistake by trying to add a HostPath and an SMB share on the same dataset.
I now have a DataSet with nothing else using it. When I setup the application I give it the host path of that Dataset and a mount path. The challenge is that I cannot see the mount path when I try to add a library path in Emby. I think this means the path is not mapping but I do not know why. I have removed and re-setup Emby several times with different combinations of data set, different mount path names with and without /'s and still no luck.
I had one time when the mount path showed up, but no files were discovered. I found out this was because the ACLs on the folder were not allowing anything to access it and I corrected it... or so I thought, now I cannot get it to show in the library path at all anymore.
Problem I have is I have no console access or anything to the Emby application (pod?). If I try the shell option with the Apps three dots menu I get this:
"WARN[ØØØØ] Unable to read /etc/rancher/k3s/k3s.yamI, please start server with --write-kubeconfig-mde to modify kube config permissions
error: error loading config file "/etc/rancher/k3s/k3s.yam1": open /etc/rancher/k3s/k3s.yæ1: permission denied"
Having never really played with Kubernetes (which I think is what is running this) I don't know where to go with this. There does not seem to be any permissions needed for the App itself so I think that is okay.
Can anyone help point me the right way?
I now have a DataSet with nothing else using it. When I setup the application I give it the host path of that Dataset and a mount path. The challenge is that I cannot see the mount path when I try to add a library path in Emby. I think this means the path is not mapping but I do not know why. I have removed and re-setup Emby several times with different combinations of data set, different mount path names with and without /'s and still no luck.
I had one time when the mount path showed up, but no files were discovered. I found out this was because the ACLs on the folder were not allowing anything to access it and I corrected it... or so I thought, now I cannot get it to show in the library path at all anymore.
Problem I have is I have no console access or anything to the Emby application (pod?). If I try the shell option with the Apps three dots menu I get this:
"WARN[ØØØØ] Unable to read /etc/rancher/k3s/k3s.yamI, please start server with --write-kubeconfig-mde to modify kube config permissions
error: error loading config file "/etc/rancher/k3s/k3s.yam1": open /etc/rancher/k3s/k3s.yæ1: permission denied"
Having never really played with Kubernetes (which I think is what is running this) I don't know where to go with this. There does not seem to be any permissions needed for the App itself so I think that is okay.
Can anyone help point me the right way?