closed-social
/
gitea
3
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3060 Commits
2 Branches
178 MiB
Tree: 9c12ed3b6e
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '9c12ed3b6e'
${ noResults }
gitea/docker/s6/openssh/setup

27 lines
737 B
Raw Normal View History

Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
​
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
Fix bug introduced in #1759 preventing ssh server to launch - ssh/setup: test directive now check if a file exist in key path instead of a folder - ssh/setup script was hanging waiting for an input about rewriting the key as the test case was returning true, when it should have been false (check if file is a folder instead of a file)
9 years ago
Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
​
Fix bug introduced in #1759 preventing ssh server to launch - ssh/setup: test directive now check if a file exist in key path instead of a folder - ssh/setup script was hanging waiting for an input about rewriting the key as the test case was returning true, when it should have been false (check if file is a folder instead of a file)
9 years ago
Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
​
Fix bug introduced in #1759 preventing ssh server to launch - ssh/setup: test directive now check if a file exist in key path instead of a folder - ssh/setup script was hanging waiting for an input about rewriting the key as the test case was returning true, when it should have been false (check if file is a folder instead of a file)
9 years ago
Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
​
Fix bug introduced in #1759 preventing ssh server to launch - ssh/setup: test directive now check if a file exist in key path instead of a folder - ssh/setup script was hanging waiting for an input about rewriting the key as the test case was returning true, when it should have been false (check if file is a folder instead of a file)
9 years ago
Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
​
Fix bug introduced in #1759 preventing ssh server to launch - ssh/setup: test directive now check if a file exist in key path instead of a folder - ssh/setup script was hanging waiting for an input about rewriting the key as the test case was returning true, when it should have been false (check if file is a folder instead of a file)
9 years ago
Docker Container: Init 1 & Initialisation - Now using a setup script before starting the app. The separation of the run script and the setup script will make service initialisation a little bit clearer - Now calling start.sh script as ENTRYPOINT and S6 as CMD. This way when running the container with just a shell script, the start.sh script will be launched before, making debugging easier - Added note about `.dockerignore` ignored during Docker Hub Automated Build
9 years ago
​
Volumed data setup changed to allow #1759 - Volumed subfolder now created up in the ENTRYPOINT script, this way they are created before S6 even starts making VOLUME. - The subfolder will be created during VOLUME creation too as ENTRYPOINT script will be run before /bin/true - SSH Keys will now be created on a single key basis not replying on the existence of /data/ssh folder
9 years ago
​
​
Add syslog & fix `/data/git` rights & SOCAT_LINK env var - Resolve #1893 - Add syslogd to output sshd log on stdout (via `docker logs`) - Enforce directory rights on `/data/git`, `/data/gogs` & `/data/ssh` - Add `SOCAT_LINK` environment variable to prevent the creation of scout links when they are not needed (see #1815)
9 years ago
​
 
  1. #!/bin/sh
  2. 

  3. # Check if host keys are present, else create them
  4. if ! test -f /data/ssh/ssh_host_key; then
  5.     ssh-keygen -q -f /data/ssh/ssh_host_key -N '' -t rsa1
  6. fi
  7. 

  8. if ! test -f /data/ssh/ssh_host_rsa_key; then
  9.     ssh-keygen -q -f /data/ssh/ssh_host_rsa_key -N '' -t rsa
  10. fi
  11. 

  12. if ! test -f /data/ssh/ssh_host_dsa_key; then
  13.     ssh-keygen -q -f /data/ssh/ssh_host_dsa_key -N '' -t dsa
  14. fi
  15. 

  16. if ! test -f /data/ssh/ssh_host_ecdsa_key; then
  17.     ssh-keygen -q -f /data/ssh/ssh_host_ecdsa_key -N '' -t ecdsa
  18. fi
  19. 

  20. if ! test -f /data/ssh/ssh_host_ed25519_key; then
  21.     ssh-keygen -q -f /data/ssh/ssh_host_ed25519_key -N '' -t ed25519
  22. fi
  23. 

  24. # Set correct right to ssh keys
  25. chown -R root:root /data/ssh/*
  26. chmod 0700 /data/ssh
  27. chmod 0600 /data/ssh/*