Does not work with ssh.socket activated ssh services
fama opened this issue · comments
Recently after installing LXC container of ubuntu, I noticed that the ssh port as modified by this role in the /etc/ssh/sshd.conf was not being respected.
This is relatively recent issue. It seems that the LXC ubuntu container running on proxmox, now uses the ssh.socket to spawn ssh service sessions on demand as opposed to have the service running all the time.
This means that:
- Either the mask for the ssh.socket needs to be configured, so that the service starts as normal: https://forum.proxmox.com/threads/auto-start-sshd.38181/page-2#post-411369
- Or the port needs to be configured in a copy of
/lib/systemd/system/ssh.socketplaced in/etc/systemd/systemdirectory?
I think the ssh service spawned on demand seems quite interesting, especially in an environment with low resources.
Jeff, as a fan of drupal, may find the following article interesting: http://0pointer.de/blog/projects/socket-activated-containers.html, how sporadic use drupal containers are spawned on demand using systemd sockets.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
This is now a more important issue to re-open as it is the default on Ubuntu 22. The correct method of using sockets with non-standard SSH ports is here: https://askubuntu.com/a/1439482