Feature req: modify ssh port

[linuxserver]

Feature req: modify ssh port

[thespad]

There's an open PR (#42) but it's waiting on the submitter to make the necessary documentation changes.

I think they got bored.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the issue template!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cwong-openfit]

hmm. i have the same issue. i set the port to 2223 but the issue is the script is hardcoded to 2222

[cwong-openfit]

thank you! :D

[LDAP]

Until #42 is merged, this is my workaround:

Create a file custom-port.sh in <config-path>/custom-cont-init.d/ with:

#!/bin/bash

# Replace 22 with your custom port
sed -i 's/-p 2222/-p 22/' /etc/services.d/openssh-server/run

[cwong-openfit]

ya. i did the same last eve.

sed -i -e 's/^USER_NAME=.*/USER_NAME=root/' -e 's/2222$/22/' /etc/services.d/openssh-server/run

i had to change the USER_NAME=root because i was getting perm denied as the regular user (911).
which i also had to change the perm and ownership of the ssh_host* files as well.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andryyy]

Doing it like this rn in a custom init script:

sed -i 's/2222/{{ env "NOMAD_PORT_[[ $task.name ]]" }}/' /etc/s6-overlay/s6-rc.d/svc-openssh-server/run
sed -i 's/2222/{{ env "NOMAD_PORT_[[ $task.name ]]" }}/' /var/run/service/svc-openssh-server/run.user

Feels dirty.

Another approach is to run socat:

socat TCP-LISTEN:{{ env "NOMAD_PORT_[[ $task.name ]]" }},fork,reuseaddr TCP:127.0.0.1:2222 &

One should consider putting that in a loop, I guess (getting dirty again):

(
while true; do
  socat TCP-LISTEN:{{ env "NOMAD_PORT_[[ $task.name ]]" }},fork,reuseaddr TCP:127.0.0.1:2222
done
) &

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[koraa]

bump. This is still highly desired. Not having a port config option in a server ist just silly for anything but the simplest servers.

[linuxmaniac]

docker-openssh-server/root/etc/s6-overlay/s6-rc.d/init-openssh-server-config/run

Lines 44 to 53 in 6ebd6fe

	# custom port
	if [[ -n "${LISTEN_PORT}" ]]; then
	sed -i "s/^#Port [[:digit:]]\+/Port ${LISTEN_PORT}"/ /etc/ssh/sshd_config
	sed -i "s/^Port [[:digit:]]\+/Port ${LISTEN_PORT}"/ /etc/ssh/sshd_config
	echo "sshd is listening on port ${LISTEN_PORT}"
	else
	sed -i "s/^#Port [[:digit:]]\+/Port 2222"/ /etc/ssh/sshd_config
	sed -i "s/^Port [[:digit:]]\+/Port 2222"/ /etc/ssh/sshd_config
	echo "sshd is listening on port 2222"
	fi

It seems you can just use LISTEN_PORT

[yoelvd]

Ok I added LISTEN_PORT as a new environment variable for my docker-compose and it works! And yet, the corresponding image documentation isn't reflecting this change. I had to come here to learn this. Thanks @linuxmaniac

[linuxmaniac]

@yoelvd please provide a PR with the changes in doc that you would like to see as a new user of the image. That would be great

[thespad]

It's not documented because we don't support it.

95% of the use cases that require it are scenarios we don't support in the first place because they are entirely ephemeral and don't provide any means of mounting a persistent /config (and thus editing sshd_config to change the listen port). Including it in the readme would imply support that we're not willing to provide.

Rather than not provide any option at all, we opted to provide an undocumented route that those with the wherewithal to understand can make use of, on the basis that if you can figure that out you're probably not going to be coming back to us for basic support for your weird setup.

(And yes, we were originally hard-coding the listen port in the sshd run command which was overriding the value(s) in sshd_config but that's no longer the case).

[drizuid]

closing as we have provided an explanation and our support stance. We will not entertain documenting it.