Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the use case for this image? #6

Open
rastasheep opened this issue Oct 26, 2016 · 12 comments
Open

What is the use case for this image? #6

rastasheep opened this issue Oct 26, 2016 · 12 comments

Comments

@rastasheep
Copy link
Owner

Hi all!

Thanks for using my image.
This is an old (forgotten) side project which wasnt updated in awhile, but with help of automatic builds on docker hub, it's still up to date and it seems that it is used widely (currently it was downloaded more than 100k times).

Can you share your use cases for this kind of image? I would like to invest some time in improvement and those informations would be more than useful to me, tnx.

@ncs-alane
Copy link

It's useful for integration testing of configuration management logic!

@rastasheep
Copy link
Owner Author

rastasheep commented Dec 19, 2016

@ncs-alane tnx, interesting i've always used vagrant for testing CM stuff :)

@KhumpuW
Copy link

KhumpuW commented Dec 28, 2016

I use it for learning Docker.
also why can't I attach to container? I assume /usr/sbin/sshd -D blocking container I/O?
then how do we make container start sshd when it start but also don't block user I/O?

@sam-rad
Copy link

sam-rad commented May 3, 2017

Really thanks for this. I was looking for a quick way to test ansible deployment and this was fantastic.

@Foorack
Copy link

Foorack commented Jul 9, 2017

@rastasheep We are currently using it as a connector for ssh tunnels. We are currently using a modified version, it would be very helpful if GatewayPorts was enabled, or if there at least were a way to toggle this. 👍

@rastasheep
Copy link
Owner Author

@Foorack tnx :) It sounds like modifying configuration in runtime with env variables would solve your use-case

@Foorack
Copy link

Foorack commented Jul 9, 2017

@rastasheep Yes, it would. Currently, we are having to build our own version with an extra line in the Dockerfile enabling GatewayPorts. That would be a great improvement! 😃

@rastasheep
Copy link
Owner Author

@Foorack awesome, i've created an issue so if anyone wants to help it's good to go .. tnx again for the feedback!

@joncamfield
Copy link

I'm interested in having a dockerized sshd on my synology, ideally one where I can:

  • customize ports (optional, can do via port fowarding)
  • create and restrict ssh users (create sudoer user, disable remote root login)
  • require ssh key login
  • have a slightly more configurable "landing" shell (for ssh tunneling, simple bash / network testing tools, quick-and-dirty SCP'ing of files)

@cognitiaclaeves
Copy link

I wanted an ability to have a jailed environment for ssh'ing into a network. I started with your image (which I later found almost in its entirety on docker's site ... but I wanted it to run as a non-privileged user. In case you're curious, my version is here.

@RamonSmit
Copy link

I'm using this in our Kubernetes cluster, just for a quick and dirty easy access to persistent volumes via sftp. Works really nice for the 5 min jobs 👍

@dagguh
Copy link

dagguh commented Apr 9, 2021

I'm using it for testing SSH scripts targeting Ubuntu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants