fix: --pull option in build and up command can not set to pull policy
#1295
+56
−22
Conversation
This file contains hidden or 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
|
Oh, we got the docker.io rate limits: Maybe we should push podman-compose-test to github and use it to avoid this problem. |
…policy. Signed-off-by: Songmin Li <lisongmin@protonmail.com>
lisongmin
force-pushed
the
fix-pull-can-not-set-to-pull-policy
branch
from
c12ff85 to
909355d
Compare
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.
The pull option behavior in podman-compose and docker-compose:
--pull--pull policy--pull-always--pull policy--pull--pull policy--pull-always--pull policyWith this PR, the
--pulloption is compat with docker-compose and previous version of podman-compose.