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.

Sign up for GitHub

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

Jump to bottom

<runCmd> errors on 0.13.2 #222

Closed
computerlyrik opened this issue Jul 18, 2015 · 1 comment
Closed

<runCmd> errors on 0.13.2 #222

computerlyrik opened this issue Jul 18, 2015 · 1 comment
Labels
fixed

Comments

@computerlyrik
Copy link
Contributor

Hey!

I have a issue, that my runCmd Command does not execute well on newly released version.
I do have a workdir configured...but i am not 100% sure, that this is the reason.

I do simply get a "non zero state" from the execution.

How do i debug (eg printout the Dockerfile used for )?

Thanks
@computerlyrik computerlyrik mentioned this issue Jul 18, 2015
Closed
@rhuss
Copy link
Collaborator

rhuss commented Jul 21, 2015

I applied your fix (since currently I don't really mind the order of WORKDIR and RUN), but I'm curious about the error message. You say "non zero state". Do you have chance to provide the output of the error message since I believe it should be more specific, too (not only for this error)

rhuss added a commit that referenced this issue Jul 21, 2015
@rhuss
Adapt documentation for #222
c76679f
@rhuss rhuss added the fixed label Jul 23, 2015
@rhuss rhuss closed this as completed in bb97f18 Aug 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rhuss @computerlyrik