playground
/
gogs
mirror of https://github.com/gogits/gogs.git
1
0
Fork 0
Code Issues Releases 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.
3001 Commits
4 Branches
53 Tags
164 MiB
Tree: a374751eb8
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a374751eb8'
${ noResults }
gogs/docker/s6/openssh/setup

27 lines
715 B
Raw Normal View History Unescape

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
#!/bin/sh
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
# Check if host keys are present, else create them
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
if ! test -f /data/ssh/ssh_host_key; then
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
ssh-keygen -q -f /data/ssh/ssh_host_key -N '' -t rsa1
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
fi
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
if ! test -f /data/ssh/ssh_host_rsa_key; then
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
ssh-keygen -q -f /data/ssh/ssh_host_rsa_key -N '' -t rsa
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
fi
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
if ! test -f /data/ssh/ssh_host_dsa_key; then
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
ssh-keygen -q -f /data/ssh/ssh_host_dsa_key -N '' -t dsa
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
fi
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
if ! test -f /data/ssh/ssh_host_ecdsa_key; then
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
ssh-keygen -q -f /data/ssh/ssh_host_ecdsa_key -N '' -t ecdsa
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
fi
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
if ! test -f /data/ssh/ssh_host_ed25519_key; then
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
ssh-keygen -q -f /data/ssh/ssh_host_ed25519_key -N '' -t ed25519
fi
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
# Set correct right to ssh keys
chown -R root:root /data/ssh/*
chmod 600 /data/ssh/*