You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the above config the allocation fails over and over again. Disabling SELinux client node wide (something I'd like to avoid) or manually adding container_file_t to /opt/nomad/data/ (which is effectively :z on a volume mount) to my nomad data directory works around the issue.
I believe this is related to the bigger conversation in hashicorp/nomad#9123 but maybe #139 could get merged so I could use security_opt = ["label=disable"] as a stop gap to disable SELinux on my container workloads that need persistent storage.
Ideally, it would be cool to just add selinuxlabel = "z" to volume_mount blocks so we can handle SELinux labeling:
It seems that I can't mount any kind of directory with the CSI hostpath plugin using
volume
andvolume_mount
directives.With the above config the allocation fails over and over again. Disabling SELinux client node wide (something I'd like to avoid) or manually adding
container_file_t
to/opt/nomad/data/
(which is effectively:z
on a volume mount) to my nomad data directory works around the issue.I believe this is related to the bigger conversation in hashicorp/nomad#9123 but maybe #139 could get merged so I could use
security_opt = ["label=disable"]
as a stop gap to disable SELinux on my container workloads that need persistent storage.Ideally, it would be cool to just add
selinuxlabel = "z"
to volume_mount blocks so we can handle SELinux labeling:on a per mount basis or inherit
selinuxlabel = "z"
fromThe text was updated successfully, but these errors were encountered: