Error: Error response from daemon: invalid volume specification: '/mnt/ssd/download:/download': Invalid mount path. /mnt/ssd/download. Following service(s) uses this path: `SMB Share`.
Can you please start a separate thread where we can troubleshoot in detail? This looks like a confirmed issue by multiple users where the previously used dataset becomes invalid.Upgrade itself went fine (22.04->22.12). Only got some Truecharts apps that won't start
Just upgraded from 22.02.4 to 22.12.0 and Plex is stuck in "DEPLOYING", was working OK before.
For the App the last application event is :
Error: Error response from daemon: invalid volume specification: '/mnt/Data1/Media/Movies:/MediaFiles/movies:ro': Invalid mount path. /mnt/Data1/Media/Movies. Following service(s) uses this path: `NFS Share`.
Container image "plexinc/pms-docker:plexpass" already present on machine
(same message even when NFS is not running)
and in Jobs:
chart.release.pod_logs Failed
Error: Received 400 response code from '/api/v1/namespaces/ix-myplex/pods/myplex-54b59f4fc9-zd9z4/log?timestamps=True&tailLines=500&container=plex'
any idea? As I don't know if it's a TrueNAS pb or Charts pb I posted here but any suggestions where I should post it?
Thanks!
App deployment can get stuck in validation when the Host Path is used between Apps and TrueNAS sharing services (e.g. SMB and NFS). | Shared host paths are considered insecure and are not recommended. Review host paths used by Apps and Sharing services and adjust paths to be unique. As a last resort that can result in system and app instability, Host Path Safety Checks can be disabled in Apps > Settings > Advanced Settings. |
Going to add this into OP, thank you.please read the 22.12.0 Known Issues
Its probably a general check to make sure user is aware of the risk. Its not done per App.I think it might go a bit deeper than that though, I have 12 apps, none of them would deploy until I removed the security check, only 4 of them were using shared paths.
Just as an FYI, although I have ranted about the insecurity of the VNC implementation, NoVNC is still entirely broken for me anyway....Has been since at least BETA 2.
[NAS-119395] - iXsystems TrueNAS Jira
ixsystems.atlassian.net
every reboot gives me this message againThis is an automatically generated mail message from mdadm
running on XXX
A Fail event had been detected on md device /dev/md127.
It could be related to component device /dev/sdc1.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active raid1 sdb1[1] sdc1[0](F)
2095040 blocks super 1.2 [2/1] [_U]
[=>...................] resync = 9.6% (201472/2095040) finish=0.1min speed=201472K/sec
unused devices: <none>
same problem here (plex). A bypass is to uncheck "Enable Host Path Safety Checks" in Apps/Stetings/Advanced setting (Kubernetes Settings).Upgrade itself went fine (22.04->22.12). Only got some Truecharts apps that won't start
Code:Error: Error response from daemon: invalid volume specification: '/mnt/ssd/download:/download': Invalid mount path. /mnt/ssd/download. Following service(s) uses this path: `SMB Share`.
just read a response by a more qualified personne than me : https://www.truenas.com/community/threads/bluefin-upgrade-discussion.105694/post-729348same problem here (plex). A bypass is to uncheck "Enable Host Path Safety Checks" in Apps/Stetings/Advanced setting (Kubernetes Settings).
I don't say it's a good one... seeing the warning when you uncheck it
Sorry, my bad. Thank you! Didn't thought of security because the paths are in "read only"... Sorry in advance if this is trivial but where can I found more informations about "steps to create unique host paths"?Please read the release notes,,,, there's a new security check.
New security checks are present for host paths in use by various sytem services. If you have host paths that are shared by multiple system services (e.g. Apps and SMB), please read the 22.12.0 Known Issues and take steps to create unique host paths for each in-use system service.
App deployment can get stuck in validation when the Host Path is used between Apps and TrueNAS sharing services (e.g. SMB and NFS). Shared host paths are considered insecure and are not recommended. Review host paths used by Apps and Sharing services and adjust paths to be unique. As a last resort that can result in system and app instability, Host Path Safety Checks can be disabled in Apps > Settings > Advanced Settings.
That's interesting, how does it know if an app is using shared paths or not if it isn't checking them all?Its probably a general check to make sure user is aware of the risk. Its not done per App.
I'm a bit confused, I don't have "Host Path Safety Checks", does it mean "Validate host path"?Please read the release notes,,,, there's a new security check.
New security checks are present for host paths in use by various sytem services. If you have host paths that are shared by multiple system services (e.g. Apps and SMB), please read the 22.12.0 Known Issues and take steps to create unique host paths for each in-use system service.
App deployment can get stuck in validation when the Host Path is used between Apps and TrueNAS sharing services (e.g. SMB and NFS). Shared host paths are considered insecure and are not recommended. Review host paths used by Apps and Sharing services and adjust paths to be unique. As a last resort that can result in system and app instability, Host Path Safety Checks can be disabled in Apps > Settings > Advanced Settings.
Seems to be renamed. I unchecked that option and all my apps started without any issues.I'm a bit confused, I don't have "Host Path Safety Checks", does it mean "Validate host path"?