-
Notifications
You must be signed in to change notification settings - Fork 8
Fixing Outrigger Dashboard on Linux #117
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a lot like docker.go from rig.
LOL. Because it is. Because I thought this would be outrigger-dashboard repo. |
…to wait for a 60 second timeout. Eeeek
commands/doctor.go
Outdated
cmd.out.Info.Printf("Docker Machine (%s) is running", cmd.machine.Name) | ||
} | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this come before the docker-machine env checks above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, you have the ENV setup correctly, but the machine not started. The machine doesn't need to be started in order to test for that env configuration. I'm not against moving the check up a step though.
* origin/develop: Display executed commands via Verbose Logging (#111) Better cross platform builds (#118) Fixing Outrigger Dashboard on Linux (#117) Fixed bug in libnss-resolver DNS resolution (#116) Added rpm to build, well, rpms Transitioned to different go base to try to head off problems with dynamically linked go binaries tweaking some build flags tweaking CGO messing with ldflags tweaked goreleaser config
No description provided.