Skip to content

Conversation

@mikemccracken
Copy link
Contributor

run section output can be long and it can be a pain to find which image failed to build in multiple-image situations.

This just adds the obvious information to the error you see at the end.

now it looks like this:

Error: run commands failed for image "layer1" in "/home/embrane/ssd/stacker/stackertest-test_basic_workings.XFZkds/stacker.yaml": execute failed: exit status 1

✅ By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

run section output can be long and it can be a pain to find which image
failed to build in multiple-image situations.

This just adds the obvious information to the error you see at the end.

Signed-off-by: Michael McCracken <mikmccra@cisco.com>
elastic/dockerfiles recently removed the actual dockerfiles from main,
so now you have to go to a specific branch to get it

Signed-off-by: Michael McCracken <mikmccra@cisco.com>
@mikemccracken mikemccracken force-pushed the 2026.01.28/main/what-file-failed branch from b5ff43c to 41da9c8 Compare January 28, 2026 22:42
ref https://docs.docker.com/reference/dockerfile/#workdir

"If the WORKDIR doesn't exist, it will be created even if it's not used
in any subsequent Dockerfile instruction."

Signed-off-by: Michael McCracken <mikmccra@cisco.com>
Copy link
Contributor

@raharper raharper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a nice improvement. Thanks for looking at this.
+1 on this after "workflow" is happy and squashed commits.

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