serversideup/docker-ssh
is a hardened SSH server container based on Debian. It works great if you need to create a secure tunnel into your cluster.
- π§ Debian-based - Get a lightweight experience, while still having Bash
- π€ Key-based auth via ENV - Grant access with the
AUTHORIZED_KEYS
environment variable - βοΈ Block IPs via ENV - Block access with the
ALLOWED_IPS
environment variable - π Unprivileged user - All SSH connections are made as an unprivileged user
- π Set your own PUID and PGID - Have the PUID and PGID match your host user
- π Hardened SSH - Prevent bot attacks and ensure quality security
- π¦ DockerHub and GitHub Container Registry - Choose where you'd like to pull your image from
- π€ Multi-architecture - Every image ships with x86_64 and arm64 architectures
This is a list of the docker images this repository creates:
Image | Image Size | Description |
---|---|---|
serversideup/docker-ssh |
A hardened SSH server based on Debian Bookworm. |
All variables are documented here:
π Variable Name | π Description | #οΈβ£ Default Value |
---|---|---|
ALLOWED_IPS | Content of allowed IP addresses (see below) | AllowUsers tunnel (allow the tunnel user from any IP) |
AUTHORIZED_KEYS | π¨ Required to be set by you. Content of your authorized keys file (see below) | |
DEBUG | Display a bunch of helpful content for debugging. | false |
PGID | Group ID the SSH user should run as. | 9999 |
PUID | User ID the SSH user should run as. | 9999 |
SSH_GROUP | Group name used for our SSH user. | tunnelgroup |
SSH_HOST_KEY_DIR | Location of where the SSH host keys should be stored. | /etc/ssh/ssh_host_keys/ |
SSH_PORT | Listening port for SSH server (on container only. You'll still need to publish this port). | 2222 |
SSH_USER | Username for the SSH user that other users will connect into as. | tunnel |
You can provide multiple keys by loading the contents of a file into an environment variable.
AUTHORIZED_KEYS="$(cat .ssh/my_many_ssh_public_keys_in_one_file.txt)"
Or you can provide the authorized_keys
file via a volume. Ensure the volume references matches the path of /authorized_keys
. The image will automatically take the file from /authorized_keys
and configure it for use with your selected user.
βΉοΈ NOTE: If both a file and variable are provided, the image will respect the value of the variable over the file.
Set this in the same context of AllowUsersThis example shows a few scenarios you can do:
ALLOWED_IPS="AllowUsers *@192.168.1.0/24 *@172.16.0.1 *@10.0.*.1"
You can see I'm forwarding 12345
to 2222
.
docker run --rm --name=ssh --network=web -p 12345:2222 localhost/ssh
This means I would connect with:
ssh -p 12345 tunnel@myserver.test
Here's a perfect example how you can use it with MariaDB. This allows you to use Sequel Pro or TablePlus to connect securely into your database server π₯³
services:
mariadb:
image: mariadb:10.11
networks:
- database
environment:
MARIADB_ROOT_PASSWORD: "myrootpassword"
ssh:
image: serversideup/docker-ssh
ports:
- target: 2222
published: 2222
mode: host
# Set the Authorized Keys of who can connect
environment:
AUTHORIZED_KEYS: >
"# Start Keys
ssh-ed25519 1234567890abcdefghijklmnoqrstuvwxyz user-a
ssh-ed25519 abcdefghijklmnoqrstuvwxyz1234567890 user-b
# End Keys"
# Lock down the access to certain IP addresses
ALLOWED_IPS: "AllowUsers tunnel@1.2.3.4"
networks:
- database
networks:
database:
services:
mariadb:
image: mariadb:10.11
networks:
- database
environment:
MARIADB_ROOT_PASSWORD: "myrootpassword"
ssh:
image: serversideup/docker-ssh
ports:
- target: 2222
published: 2222
mode: host
# Set the Authorized Keys of who can connect
environment:
# Lock down the access to certain IP addresses
ALLOWED_IPS: "AllowUsers tunnel@1.2.3.4"
configs:
- source: ssh_authorized_keys
# Mount the file to "/authorized_keys". The image will handle everything else
target: /authorized_keys
mode: 0600
networks:
- database
# Define the config to be used
configs:
ssh_authorized_keys:
file: ./authorized_keys
networks:
database:
- DockerHub to browse the images.
- Discord for friendly support from the community and the team.
- GitHub for source code, bug reports, and project management.
- Get Professional Help - Get video + screen-sharing help directly from the core contributors.
As an open-source project, we strive for transparency and collaboration in our development process. We greatly appreciate any contributions members of our community can provide. Whether you're fixing bugs, proposing features, improving documentation, or spreading awareness - your involvement strengthens the project. Please review our code of conduct to understand how we work together respectfully.
- Bug Report: If you're experiencing an issue while using these images, please create an issue.
- Feature Request: Make this project better by submitting a feature request.
- Documentation: Improve our documentation by submitting a documentation change.
- Community Support: Help others on GitHub Discussions or Discord.
- Security Report: Report critical security issues via our responsible disclosure policy.
Need help getting started? Join our Discord community and we'll help you out!
All of our software is free an open to the world. None of this can be brought to you without the financial backing of our sponsors.
No bronze sponsors yet. Become a sponsor β Β Β Β Β Β ΒWe're Dan and Jay - a two person team with a passion for open source products. We created Server Side Up to help share what we learn.
- π Blog - Get the latest guides and free courses on all things web/mobile development.
- π Community - Get friendly help from our community members.
- π€΅ββοΈ Get Professional Help - Get video + screen-sharing support from the core contributors.
- π» GitHub - Check out our other open source projects.
- π« Newsletter - Skip the algorithms and get quality content right to your inbox.
- π₯ Twitter - You can also follow Dan and Jay.
- β€οΈ Sponsor Us - Please consider sponsoring us so we can create more helpful resources.
If you appreciate this project, be sure to check out our other projects.
- The Ultimate Guide to Building APIs & SPAs: Build web & mobile apps from the same codebase.
- Building Multi-Platform Browser Extensions: Ship extensions to all browsers from the same codebase.
- Bugflow: Get visual bug reports directly in GitHub, GitLab, and more.
- SelfHost Pro: Connect Stripe or Lemonsqueezy to a private docker registry for self-hosted apps.
- AmplitudeJS: Open-source HTML5 & JavaScript Web Audio Library.
- Spin: Laravel Sail alternative for running Docker from development β production.
- Financial Freedom: Open source alternative to Mint, YNAB, & Monarch Money.