Restricted SSH server which allows SFTP access only. This image is meant to provide an ability to update content in data containers. You would normally make a constellation of your service, a data container, and the sftp-server container.
The sftp-server container is configured at runtime with environment variables to match the configuration of the main service. The environment variables are:
AUTHORIZED_KEYS- contains the public SSH keys for the users who will be allowed to upload.
USERID- The numeric id of the
dataaccount. Defaults to 33.
GROUPID- The numeric id of the
datagroup. Defaults to 33.
/home/data- Directory where all your data is
HostKeysgo here. Mount a volume here so they don't get regenerated all the time the container boots.
It is easiest if you use docker-compose. Then you can specify the authorized SSH keys in a block declaration:
sftpserver: image: r3pek/sftp-server ports: - <PORT>:22 environment: AUTHORIZED_KEYS: | ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA4FhFro3H....vg0hrC3s0= My First CERT ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAteQ38qb7....uC839w== Second authorized key USERID: 500 GROUPID: 500 volumes: - <DATADIR>:/home/data httpd: image: httpd ports: - 80:80 volumes_from: - htdocs htdocs: image: tianon/true volumes: - <DATADIR>:/usr/local/apache2/htdocs
When started you can upload data into the container as the
sftp -P <PORT> data@<DOCKER-HOST>