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

"Stack new" goes through normal init process, loads existing stack.yaml #2110

rrnewton opened this issue May 6, 2016 · 1 comment


Copy link

@rrnewton rrnewton commented May 6, 2016

Is this the intended behavior? I was just in an empty directory, trying to initialize it with:

$ stack new simple-library
Cannot find 'docker' in PATH.  Is Docker installed?

Why the error? Well, that's because this is a checkout of a repo that has a stack.yaml higher up, in a parent directory. The stack.yaml in the parent directory has docker enabled, and I happen to have it checkout out on a machine that doesn't have Docker.

I assumed that since stack new is about creating new projects, it would not go through the normal search process for a stack.yaml configuration.

In my case, I could move the directory somewhere else, stack new, and then move it back. Subsequently everything would work fine of course.

stack version: 1.1.0

mgsloan added a commit that referenced this issue May 6, 2016
@mgsloan mgsloan added the type: bug label May 6, 2016
@mgsloan mgsloan added this to the P2: Should milestone May 6, 2016
mgsloan added a commit that referenced this issue May 6, 2016
Copy link

@mgsloan mgsloan commented May 7, 2016

@rrnewton Good point, fixed in HEAD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants