/stack

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

Building a container image drops a .stack-work dir in the current working (sub)directory #1975

Closed
dysinger opened this Issue Mar 31, 2016 · 1 comment

Comments

Assignees

@dysinger dysinger

Labels
Projects
None yet
Milestone
No milestone
2 participants
@dysinger @mgsloan
@dysinger
Contributor

dysinger commented Mar 31, 2016

I built an image with stack image container in a subdir and I see a left-over cruft directory left behind in the sub-directory.

% find .stack-work 
.stack-work
.stack-work/image
.stack-work/image/0
.stack-work/image/0/usr
.stack-work/image/0/usr/local
.stack-work/image/0/usr/local/bin
.stack-work/image/0/usr/local/bin/xyz
.stack-work/image/0/Dockerfile

@dysinger dysinger self-assigned this Mar 31, 2016

@dysinger dysinger added ready and removed ready labels Mar 31, 2016

@mgsloan

This comment has been minimized.

Sign in to view
Collaborator

mgsloan commented Mar 31, 2016

Hmm, yeah, that should probably go in the .stack-work at the project root (next to stack.yaml)

@dysinger dysinger added ready component: docker type: bug labels Apr 1, 2016

@dysinger dysinger added in progress awaiting pull request and removed ready in progress labels Apr 6, 2016

@dysinger dysinger referenced this issue Apr 6, 2016

Closed

Don't drop .stack-work in the current dir during `stack image container` #2007

@dysinger dysinger closed this in 7519994 Apr 7, 2016

@dysinger dysinger removed in progress awaiting pull request labels Apr 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment