This approach is ideal when you regularly connect to your containers from a remote host as it streamlines the two-step 'SSH then docker exec' sequence into a single memorable command. Using Dockssh makes it easy to SSH into a large number of Docker containers.

This was set as container-password-here in our Redis record above. You'll be prompted for the container's password when you connect. The firewall is opened to allow incoming connections using the port. Redis-cli set dockssh:my-container:pass 'container-password-here'ĭockssh listens on port 22022 by default. Next, define the containers you want to expose by adding a Redis record with the container's name and a password for SSH connections: You must first install Redis to store Dockssh's configuration data: In the latter case, the key would be baked into the image, visible to anyone with access. Copy in a public key from your working directory, either with a docker cp command or a COPY instruction in the Dockerfile. This way the SSH daemon can verify your machine's identity when you connect.Īlter your Dockerfile to setup the. You'll need to create a key pair on your client machine, then copy the public part into the container. RUN echo 'sshuser:Changeme' | changepasswdĪ more secure way is to set up SSH key authentication. You could assign a password to your sshuser account and login with that: Next you need to setup an authentication system.

You could replace this with your application's binary. Execution is then handed off to Bash as the container's foreground process. For example, if you wanted to set up the same SSH tunnel as above, youd enter 8888 as the source port and localhost:1234 as the destination. The use of ENTRYPOINT ensures the SSH service always starts when the container does. For 'Destination', enter the destination address and port in the form remoteaddress:remoteport.

The -s switch sets the user's default login shell to Bash. This creates a new user called sshuser with a home directory ( -m).

Docker ssh tunnel