Skip to content

Don't delete the working dir for config changes #1

@kmccloud

Description

@kmccloud

Currently, when there is a docker container start event the script /generateConfig.sh is ran.
The "init" method deletes the CONFIG_DIR.
We copy our id_rsa and authorized files to this directory when a container starts thus they get removed by generateConfig.sh.
Also, if we have several containers running, one for each user that might try to ssh in, their keys get deleted too.

If the generateConfig.sh script were change to simply remove he sshpiper_upstream files, it will recreate them in the parseConfig method.

    init() {
      # Remove existing configuration
      rm -rf ${CONFIG_DIR}/*/sshpiper_upstream
      # Ensure configuration folder exists
      mkdir -p ${CONFIG_DIR}
    }

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions