DRAFT: Update Dockerfile content #650
Draft
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
alan-forbes-cp
changed the title
alan-forbes-cp
changed the title
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.
Overview
Having created separate "test" dockerfile images from
mainin the immediately previous PR, point again at the original production images and content.Reason for change
The previous PR created new "test" docker file images which can - in theory - be updated by Dev branches (TBD). Now restore original production images and content.
Description of change
Restore original dockerfile content and production image names.
Anything else we should know?
This implements a suggested work-around regarding the reading/writing of "test" docker images from non-default branches.
Further testing will follow to confirm its operation in context.