Skip to content

Client Not Compatible with Org That Has VNM Enabled #80

Open

Description

@coolguy-5

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""

Activity

  1. changed the title [-]Client Not Compatible With Org That Has VNM Enabled[/-] [+]Client Not Compatible with Org That Has VNM Enabled[/+] on Aug 4, 2025
  2. self-assigned this
    on Aug 4, 2025
  3. kellenanker7 commented on Aug 4, 2025

    @kellenanker7
    Contributor

    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?

  4. coolguy-5 commented on Aug 7, 2025

    @coolguy-5
    ContributorAuthor

    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 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

sdm-clientStrongDM Client chart

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions