Skip to content

Allow running sshd in dstack runs#2178

Merged
jvstme merged 1 commit intomasterfrom
issue_2177_allow_second_sshd
Jan 7, 2025
Merged

Allow running sshd in dstack runs#2178
jvstme merged 1 commit intomasterfrom
issue_2177_allow_second_sshd

Conversation

@jvstme
Copy link
Copy Markdown
Collaborator

@jvstme jvstme commented Jan 7, 2025

  • Set PidFile=no to avoid dstack's sshd getting killed when the user's sshd is restarted
  • Do not edit /etc/ssh/sshd_config to avoid overwriting user's settings

Fixes #2177

- Set `PidFile=no` to avoid `dstack`'s sshd
  getting killed when the user's sshd is restarted
- Do not edit `/etc/ssh/sshd_config` to avoid
  overwriting user's settings
@jvstme jvstme requested a review from un-def January 7, 2025 14:06
@jvstme jvstme merged commit 87fe51f into master Jan 7, 2025
@jvstme jvstme deleted the issue_2177_allow_second_sshd branch January 7, 2025 14:18
pranitnaik43 pushed a commit to bahaal-tech/dstack that referenced this pull request Feb 9, 2025
- Set `PidFile=no` to avoid `dstack`'s sshd
  getting killed when the user's sshd is restarted
- Do not edit `/etc/ssh/sshd_config` to avoid
  overwriting user's settings
pranitnaik43 pushed a commit to bahaal-tech/dstack that referenced this pull request Mar 4, 2025
- Set `PidFile=no` to avoid `dstack`'s sshd
  getting killed when the user's sshd is restarted
- Do not edit `/etc/ssh/sshd_config` to avoid
  overwriting user's settings
pranitnaik43 pushed a commit to bahaal-tech/dstack that referenced this pull request Mar 5, 2025
- Set `PidFile=no` to avoid `dstack`'s sshd
  getting killed when the user's sshd is restarted
- Do not edit `/etc/ssh/sshd_config` to avoid
  overwriting user's settings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot use my own SSH server in runs

2 participants