Adding Pull Policy to Latest Images #461
Merged
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.
Changes
Summary
This pull request adds the
pull_policy: always
option to ensure that Docker Compose always pulls the latest images for the following services:frontend
(./build/docker-compose-no-build.yaml
)backend
(./build/docker-compose-no-build.yaml
)ui
(./build/docker-compose.yaml
and./build/docker-compose-no-build.yaml
)Note: This change requires Docker Compose version 3.7 or later.
Issues Fixed
Previously, if a user had an older image in their repository, docker would start up the preexisting image, even if it wasn't necessarily the latest image in the remote repository.
Motivation and Context
To ensure that the latest versions of the images are always used, reducing the risk of running outdated versions.
Testing
Testing Configurations
frontend
,backend
,ui
Steps to Reproduce
pull_policy: always
.docker-compose pull
to pull the latest images.docker-compose up -d
to start the services.Sample Output
N/A - This change does not modify the output of Strelka.
Checklist