-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
instead we should start it explicitly using supervisor API. Especially the |
@csweichel Can we listen to ssh tcp port and activate the server if one tries to connect, i.e. have some kind of proy? |
Inetd style socket activation could also do the trick |
/schedule |
@csweichel: Issue scheduled in the IDE team (WIP: 0) In response to this:
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. |
/assign @aledbf |
Right now, dropbear is started in every workspace (even if we don't use it)
Reasons:
The text was updated successfully, but these errors were encountered: