stable
Clone or download
Read-only
This contribution does 2 things: * it writes the SSH host keys directly under the persisted directory of the container * it makes sure existing keys have the proper permissions (mainly to be sure we do not have issues with keys created in the past) This should resolve the issue we are seeing on live instance where SSHd does not start because it considers the private key is exposed too much. Closes request #35851: SSHd process does not start in container images Change-Id: Ie954a143428daac55e55ff61aec83c31c07e0b8e
Modified Files
Name | ||||
---|---|---|---|---|
M | plugins/tee_container/docker/Dockerfile | +0 | −3 | Go to diff View file |
M | plugins/tee_container/docker/sshd_config | +3 | −3 | Go to diff View file |
M | plugins/tee_container/include/StartContainerCommand.php | +0 | −6 | Go to diff View file |
M | src/tuleap-cfg/Command/Docker/SSHDaemon.php | +29 | −9 | Go to diff View file |
M | src/tuleap-cfg/Command/StartCommunityEditionContainerCommand.php | +0 | −6 | Go to diff View file |
M | tools/docker/tuleap-community-edition/Dockerfile | +0 | −2 | Go to diff View file |
M | tools/docker/tuleap-community-edition/sshd_config | +3 | −3 | Go to diff View file |