It was designed for a single user access. For multiple users, you can run multiple containers. It’s what I do. That way, I can have different access settings and volume mappings for each user.
Hello. Found this old thread that raised the same question I have. I love the openssh container but running on NAS behind firewall with sslh used to redirect incoming requests between this container for ssh and web server for ssl. I can’t find a good way to further redirect to different containers based on user so figured I’d come here and bring up this question again. Recognizing this container is designed for single user access, is there any way to set it up for multiple user access, or request a version of the container that will support it? I am relatively familiar with linux based systems, but am a docker / alpine / linuxserver newbie. I have been able to use standard commands and the configuration script to create a new user with home directory, and can log in or switch directly to that user in the container itself (connecting via docker exec), and the SSHD service will authenticate the user but appears unable to actually switch to that user after authentication, so even just understanding how the container is set up to restrict access to a single user would help (does not appear to be thorugh sshd configuration from what Ic an tell?) Thank you!
Simply adjust “REMOTE_SSH_SERVER” variable to your IP (and port if needed)… and deploy. Open a browser tab to your-ip:3000 and you’ll be prompted for a username.
It’s also very easy to reverse proxy through swag rather than exposing a port on your router, if you need remote access.