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.

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

[local app] Do not always start dropbear #4848

Closed
aledbf opened this issue Jul 16, 2021 · 6 comments · Fixed by #6348
Closed

[local app] Do not always start dropbear #4848

aledbf opened this issue Jul 16, 2021 · 6 comments · Fixed by #6348

Comments

@aledbf
Copy link
Member

aledbf commented Jul 16, 2021

Right now, dropbear is started in every workspace (even if we don't use it)
Reasons:

  • Generation of the SSH key consumes too much CPU
@csweichel
Copy link
Contributor

instead we should start it explicitly using supervisor API. Especially the dropbearkey operation is expensive in terms of CPU and should only be done when needed.

@akosyakov
Copy link
Member

@csweichel Can we listen to ssh tcp port and activate the server if one tries to connect, i.e. have some kind of proy?

@csweichel
Copy link
Contributor

Inetd style socket activation could also do the trick

@csweichel
Copy link
Contributor

/schedule

@roboquat
Copy link
Contributor

@csweichel: Issue scheduled in the IDE team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@csweichel
Copy link
Contributor

/assign @aledbf

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

Successfully merging a pull request may close this issue.

5 participants