Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Volume not mounted if CONNECT_TO is set in ENVS #8

Open
LionelJouin opened this issue May 27, 2021 · 1 comment
Open

Volume not mounted if CONNECT_TO is set in ENVS #8

LionelJouin opened this issue May 27, 2021 · 1 comment
Assignees
@LionelJouin
Labels
bug Something isn't working

Comments

@LionelJouin
Copy link
Member

The volume mounted in the NSC is hardcoded in the webhook, so if the CONNECT_TO environment variable is set to another directory than /var/lib/networkservicemesh, the NSC containers injected will not be able to communicate with the NSM API.

Steps to reproduce

  1. Add the CONNECT_TO variable to the ENVS in the environment variables of the webhook
- name: NSM_ENVS
  value: NSM_CONNECT_TO=unix:///new-path/nsm.io.sock
  1. Set the CONNECT_TO (or LISTEN_ON for nsmgr) environment variable for the other NSM components
  2. Deploy NSM + webhook
  3. Deploy an NSM application (NSC + NSE)

new-path is not mounted, so the NSC will not start.
@denis-tingaikin
Copy link
Member

Be free to provide PR :)

@denis-tingaikin denis-tingaikin added the bug Something isn't working label May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LionelJouin LionelJouin

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LionelJouin @denis-tingaikin