We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To solve this temporarily do the following:
make addkey
docker-compose up -d --force
ssh-add -L
The text was updated successfully, but these errors were encountered:
Verified times when keys are "lost":
Rationale:
Containers have rule restart: unless-stopped which means they get restarted in case of OS or Docker gets rebooted.
restart: unless-stopped
But as adding keys is not part of Docker itself, that cannot be automised to happen on reboots.
Possible solution:
Change adding keys to manual operation ALWAYS. It might be security related decision as now we add default keys without asking on up'ping.
Sorry, something went wrong.
There might be other occasions ofc when the whole SSH_AGENT stuff gets somehow disrupted.
plist could help on mac #61
No branches or pull requests
To solve this temporarily do the following:
make addkey
docker-compose up -d --force
ssh-add -L
You should now have your keys in the container. If not - pray to god.
The text was updated successfully, but these errors were encountered: