title: git clone (SSH) gets reaped by supervisord run in docker
body: <p>I'm trying to create application for hosting remote git repositories. What I'm trying to do is to allow user clone the repository by SSH, I'm using supervisord to serve my application and sshd, but when I'm trying to clone repository I get:</p>
  
  <pre><code>$ git clone git@address:/repositories/some-repo
  Cloning into 'some-repo'...
  fatal: Could not read from remote repository.
  
  Please make sure you have the correct access rights
  and the repository exists.
  </code></pre>
  
  <p>and in supervisord log I can see:</p>
  
  <pre><code>[date] INFO reaped unknown pid [PID]
  </code></pre>
  
  <p>So in my opinion it's just supervisord who is killing all not known PIDs.
  I'm sure that I have set correct access rights to my repositories and my key is added to <code>authorized_keys</code> file. My current supervisord config is:</p>
  
  <pre><code>[supervisord]
  logfile = /tmp/supervisord.log
  directory = /tmp
  childlogdir = /tmp
  
  [program:app-sshd]
  command=/usr/sbin/sshd -D
  
  [program:app-uwsgi]
  command = /usr/local/bin/uwsgi --ini /my/path/uwsgi.ini
  stopsignal=INT
  
  [program:app-nginx]
  command = /usr/sbin/nginx
  </code></pre>
  
  <p>Is there any way to allow git connections in supervisor or will I need to replace my docker container with virtual machine to proceed with this project?</p>