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
{{ message }}
Repository navigation
Client Not Compatible with Org That Has VNM Enabled #80
After deploying SDM-client, the pod crashes with this error:
time="2025-08-04T17:42:33Z" level=warn msg="[LazyTUN] failed to start" error="permission denied: insufficient permitted privileges. want "cap_net_admin", have "cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap=ep""
this should be doable by adding the missing capability to pod.spec.containers.securityContext.capabilities.add. were you envisioning this being behind a value akin to strongdm.vnmEnabled: false?
I'm not sure. Ideally, it shouldn't require any input from the end-user, but maybe its the only way and in that case strongdm.vnmEnabled is good enough 👍
Activity
[-]Client Not Compatible With Org That Has VNM Enabled[/-][+]Client Not Compatible with Org That Has VNM Enabled[/+]kellenanker7 commentedon Aug 4, 2025
this should be doable by adding the missing capability to
pod.spec.containers.securityContext.capabilities.add. were you envisioning this being behind a value akin tostrongdm.vnmEnabled: false?coolguy-5 commentedon Aug 7, 2025
I'm not sure. Ideally, it shouldn't require any input from the end-user, but maybe its the only way and in that case strongdm.vnmEnabled is good enough 👍