-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
_prepare_build_container
runner calls should not output to stdout
All output generated by the container runtime during the `_prepare_build_container` stage should not be included in stdout - we should redirect it to stderr, as the user is just using skipper as a wrapper to run commands like make, run etc - they don't care that as a side-effect of running their commands a container is being built, and they don't want the output from that build process to be included in the stdout for the commands they wrap with skipper. This allows users to do things like VERSION=$(skipper make get_version) without having the build process output be included in their VERSION env var. Surprisingly (to me), docker/podman build output such as: ``` Step 13/18 : ENV GOPATH=/go ---> Using cache ---> 152ad1ea9005 Step 14/18 : ENV GOCACHE=/go/.cache ---> Using cache ---> 4b6a4256c84f Step 15/18 : ENV PATH=$PATH:/usr/local/go/bin:/go/bin ---> Using cache ---> 56bee68a9cda Step 16/18 : COPY . . ``` Goes to stdout and not stderr, and this causes this kind of pollution.
- Loading branch information
Showing
4 changed files
with
33 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters