Investigation: Can we inject gitlab-sshd directly inside a workspace instead of expecting OpenSSH pre-installed
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
MR: Pending
Description
As a user, I want to be able to SSH into any workspace without having to configure it during container build time.
Why we implemented our own SSHD solution is a blog post by GitLab which highlights why we built our own SSHD solution. We should dogfood that. Instead of expecting users to pre-install OpenSSH server into their workspace, we should automatically inject the sshd into the workspace(like we do for editors/IDEs).
GitLab SSHD is an internal package of gitlab-shell. Can and should it be used outside of it?
Notes
Acceptance Criteria
-
Users no longer need to do some special configuration in their container to be able to SSH into it in a workspace.
Technical Requirements
TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.]
Design Requirements
TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.]
Impact Assessment
TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]
User Story
TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]