Singular Dockerfile to build the image. [WIP] #8
Conversation
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
|
It seems as though copying from an earlier stage in the build made the outrigger-dashboard binary non-executable, and the use of scratch as the base image meant that sh and chmod were unavailable to fix it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I gave this a shot, if nothing else as an experiment. In practice it is building, but the container crashes with "standard_init_linux.go:187: exec user process caused "no such file or directory" in the docker logs.
The multiple build stages seem to work nicely, which I take as an intriguing sign that if we chose to split our language runtimes we could still "pipeline" betwixt them to produce finalized build artifacts.