mysql ssh tunnel putty initial communication

#Mysql ssh tunnel putty initial communication how to
#Mysql ssh tunnel putty initial communication full

The container image makes it relatively easy for us to do so.īy using the PUBLIC_KEY_FILE parameter, we can add a public key to the authorized_keys file.

Of course we want to make it easy to connect to this SSH tunnel.

#Mysql ssh tunnel putty initial communication full

You can find the full contents of the file in this gist. Changing it to ‘yes’ could cause some security issues, but nothing to worry about in your development environment. Our own config file is just the default config file taken from the container, but with the AllowTcpForwarding setting changed. openssh/sshd_config:/config/ssh_host_keys/sshd_config To override this setting, we’ll have to configure a volume to use our own sshd_config file. This can be done by overriding a setting in the sshd_config file. To properly connect to MySQL, we need to allow TCP forwarding. This image exposes port 2222 by default to connect with SSH and we will map this port to the same port on our host machine.

We are using the linuxserver/openssh-server image, which offers us some options to customize the service. Let’s focus on the sshtunnel service we added. openssh/sshd_config:/config/ssh_host_keys/sshd_config ~/.ssh/id_rsa.pub:/etc/tunnel/id_rsa.pub

Image: ghcr.io/linuxserver/openssh-server var/run/docker.sock:/var/run/docker.sock:ro Here’s the updated docker-compose file for running Traefik: version: '3' The solution here is to not use Traefik but to spin up a container next to our Traefik container which serves as an SSH tunnel. This is not a proper solution since we don’t want to bother with port management. This means we would still have to map each running database container to a specific port on the host machine. In short, Traefik won’t be able to determine the right container based on domain name. There are some technical reasons why the setup used for http endpoints won’t work for MySQL. Unfortunately, Traefik is not the optimal solution for us. That’s very annoying and we can do better! Configure a Docker port for MySQL Now we need to go to our database tool and change the connection settings before we can connect again. Only this time port 3306 is mapped to port 54122.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĢbb260f8969e mysql:latest 'docker-entrypoint.s…' 14 seconds ago Up 13 seconds 33060/tcp, 0.0.0.0:54122->3306/tcp mysqlĩa99e24681e8 httpd:2.4-alpine 'httpd-foreground' 10 minutes ago Up 13 seconds 0.0.0.0:54123->80/tcp apache Let’s restart our containers and take another look at the output of running docker-compose ps. But there is an annoyance luring around the corner.Įvery now and then, we stop our containers and start them up again - perhaps daily - if we need to switch projects. Hurray! We have a container with MySQL running and we can connect to it through port 53900. '.entrypoints=web'Īfter running docker-compose up, we end up with the following docker containers running: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĩa99e24681e8 httpd:2.4-alpine 'httpd-foreground' 8 seconds ago Up 7 seconds 0.0.0.0:53901->80/tcp apacheĠbb272d37f00 mysql:latest 'docker-entrypoint.s…' 8 seconds ago Up 7 seconds 33060/tcp, 0.0.0.0:53900->3306/tcp mysql Let’s take the demo `docker-compose` file from the last blog post, but this time we’ll also add a MySQL database: version: '3.8' This can be done for your http (and https) needs, but it’s also possible to have a similar setup for your database.

#Mysql ssh tunnel putty initial communication how to

That blog post described how to set up the Traefik proxy and route all your traffic to the correct container without having to rely on the ports exposed by your container. About a year ago, I wrote about managing your ports with Traefik in your local development environment.