-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(core): show Docker build output for BundlingDockerImage.fromAss…
…et() (#12001) Remove the `-q` option and use a known tag derived from the path to the Dockerfile and the build options. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
- Loading branch information
Showing
2 changed files
with
37 additions
and
38 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
@jogold
In my experience using
BundlingDockerImage.cp
, which is the only place that expects a return fromdockerExec
, the stdout is missing and this should be astdio: 'pipe'
as discussed at https://stackoverflow.com/questions/35689080/how-to-read-child-process-spawnsync-stdout-with-stdio-option-inherit.My CICD pipelines run in docker and so the normal image building with volumes process doesn't work, and I am building the image and using cp to extract the artifact.