Question 1

How to set up Docker-SSH with public key authentication?

Accepted Answer

Mount an authorized_keys file as a volume and set AUTH_MECHANISM=publicKey with AUTHORIZED_KEYS pointing to the file, as shown in the README example. Ensure the key permissions are correct to avoid authentication failures.

Question 2

Docker-SSH vs installing SSH inside a container: which is better?

Accepted Answer

Docker-SSH is better for adhering to single-process containers and avoiding image bloat, but installing SSH internally might be simpler for static environments. Docker-SSH's compositional approach adds flexibility but requires managing an extra service.

Question 3

Is Docker-SSH secure for production use?

Accepted Answer

It can be secure if configured with strong authentication (e.g., public keys) and in isolated networks, but mounting the Docker socket is a risk. The README warns against noAuth and recommends careful setup to mitigate privilege escalation.

Question 4

Can Docker-SSH access multiple containers at once?

Accepted Answer

No, it currently only targets one container per instance, with 'Access multiple containers' listed as a todo feature. For multiple containers, you need to run separate Docker-SSH instances or use alternative methods.

Question 5

How to disable the web terminal in Docker-SSH?

Accepted Answer

Set the environment variable HTTP_ENABLED=false when running the container, as mentioned in the Web Terminal section. This disables the HTTP port 8022 and reduces the attack surface.

Question 6

What are the alternatives to Docker-SSH for container access?

Accepted Answer

Alternatives include using docker exec directly from the host, tools like nsenter, or managed services like Kubernetes exec. Docker-SSH is unique for providing SSH protocol access without container modifications.

docker-ssh

What is docker-ssh?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions