kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
rodzic
8bcb5a2576
commit
c900cb4244
|
@ -36,8 +36,8 @@ The architectures supported by this image are:
|
|||
|
||||
## Application Setup
|
||||
|
||||
If `PUBLIC_KEY` or `PUBLIC_KEY_FILE`, or `PUBLIC_KEY_DIR' variables are set, the specified keys will automatically be added to `authorized_keys`. If not, the keys can manually be added to `/config/.ssh/authorized_keys` and the container should be restarted.
|
||||
Removing `PUBLIC_KEY` or `PUBLIC_KEY_FILE` variables from docker run environment variables will not remove the keys from `authorized_keys`. `PUBLIC_KEY_FILE` and `PUBLIC_KEY_DIR' can be used with docker secrets.
|
||||
If `PUBLIC_KEY` or `PUBLIC_KEY_FILE`, or `PUBLIC_KEY_DIR` variables are set, the specified keys will automatically be added to `authorized_keys`. If not, the keys can manually be added to `/config/.ssh/authorized_keys` and the container should be restarted.
|
||||
Removing `PUBLIC_KEY` or `PUBLIC_KEY_FILE` variables from docker run environment variables will not remove the keys from `authorized_keys`. `PUBLIC_KEY_FILE` and `PUBLIC_KEY_DIR` can be used with docker secrets.
|
||||
|
||||
We provide the ability to set and allow password based access via the `PASSWORD_ACCESS` and `USER_PASSWORD` variables, though we as an organization discourage using password auth for public facing ssh endpoints.
|
||||
|
||||
|
@ -54,7 +54,7 @@ This container can be set up with a mounted folder for incoming backups, and rsy
|
|||
|
||||
It is also possible to run multiple copies of this container with different ports mapped, different folders mounted and access to different private keys for compartmentalized access.
|
||||
|
||||
**TIPS**
|
||||
#### TIPS
|
||||
You can volume map your own text file to `/etc/motd` to override the message displayed upon connection.
|
||||
You can optionally set the docker argument `hostname`
|
||||
|
||||
|
|
Ładowanie…
Reference in New Issue