do not use sshd in docker container

[cguentherTUChemnitz]

If i see it right, the ssh port 22 is mapped to 24 to provide ssh access to the container. Using sshd inside docker containers is widely discussed as an antipattern. If you just want to access the containers shell you should access it by ssh to your docker's host and run docker exec -it phabricator_container_name /bin/bash. That will start the /bin/bash shell of your running container instance. Other tasks like backups is more detailed discussed here: https://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/

best, Christian

[hach-que]

The new image that's a work in progress (on the newconf branch) removes the SSH on port 24.

On Fri., 22 Apr. 2016, 18:07 cguentherTUChemnitz, notifications@github.com wrote:

If i see it right, the ssh port 22 is mapped to 24 to provide ssh access to the container. Using sshd inside docker containers is widely discussed as an antipattern. If you just want to access the containers shell you should access it by ssh to your docker's host and run docker exec -it phabricator_container_name /bin/bash. That will start the /bin/bash shell of your running container instance. Other tasks like backups is more detailed discussed here: https://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/

best, Christian

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/hach-que-docker/phabricator/issues/21

[hach-que]

The new image no longer ships an administrative SSHD on port 24 (it still does ship SSHD on port 22 for repository access).