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.

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

Garden fails with cryptic error msg when called outside of git repo #1194

Closed
baspetersdotjpeg opened this issue Sep 17, 2019 · 0 comments · Fixed by #1198
Closed

Garden fails with cryptic error msg when called outside of git repo #1194

baspetersdotjpeg opened this issue Sep 17, 2019 · 0 comments · Fixed by #1198
Assignees
Labels
bug priority:low Low priority issue or feature

Comments

@baspetersdotjpeg
Copy link
Contributor

Bug

Current Behavior

When calling Garden outside of an initialized git repository, it fails with a rather cryptic error message.

Expected behavior

A concise error message with an explanation as to why it fails.

Reproducible example

  1. Run Garden outside of a Git repo (but all the right config files in place)
  2. Run git init and do it again

Workaround

N/A

Suggested solution(s)

N/A

Additional context

N/A

Your environment

% garden version
0.10.9
% kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
% docker version
Client: Docker Engine - Community
Version: 19.03.0-rc2
API version: 1.40
Go version: go1.12.5
Git commit: f97efcc
Built: Wed Jun 5 01:37:53 2019
OS/Arch: darwin/amd64
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

garden version

kubectl version

docker version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug priority:low Low priority issue or feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants