Skip to content

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

Merged
merged 4 commits into from
Nov 10, 2017
Merged

Fixing Outrigger Dashboard on Linux #117

merged 4 commits into from
Nov 10, 2017

Conversation

febbraro
Copy link
Member

No description provided.

Copy link
Contributor

@grayside grayside left a 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.

@grayside
Copy link
Contributor

LOL. Because it is. Because I thought this would be outrigger-dashboard repo.

cmd.out.Info.Printf("Docker Machine (%s) is running", cmd.machine.Name)
}
}

Copy link
Contributor

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?

Copy link
Member Author

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.

@febbraro febbraro merged commit 3f6406a into develop Nov 10, 2017
@febbraro febbraro deleted the bug/linux-dashboard branch November 10, 2017 20:20
@grayside grayside added this to the v2.0 milestone Nov 10, 2017
grayside pushed a commit that referenced this pull request Nov 11, 2017
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants