Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

ssh not ready yet for skeg run or skeg connect #1

Closed
justone opened this issue May 21, 2016 · 1 comment
Closed

ssh not ready yet for skeg run or skeg connect #1

justone opened this issue May 21, 2016 · 1 comment
Labels
bug

Comments

@justone
Copy link
Member

justone commented May 21, 2016

When skeg run or skeg connect is run, the container needs a split second to start up and get ssh running before attempting the connection. Right now, there are times where the connection fails. The workaround is to attempt connecting again.

Skeg should attempt to connect to the tcp port that ssh will listen on and then connect after it's determined that ssh is running.
@justone justone added the bug label May 21, 2016
@justone
Copy link
Member Author

justone commented Nov 10, 2016

This was fixed in v0.2.1

@justone justone closed this as completed Nov 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@justone