-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lifecycle only gets remote or local image, without concern for pulling #91
Conversation
@ashwin-venkatesh @joaopapereira I wonder if it makes sense to take the pulling logic out of I'm thinking about the pull logs and this upcoming bug buildpacks/roadmap#49, both of which would be less complicated if the pull logic lived in pack Additionally I'm worried that pack might print confusing logs if it can't determine whether the image was pulled or not. |
- We want to ensure that lifecycle does not return an error in the situation where we can pull from remote but the image only exists locally [buildpacks/pack#90] Signed-off-by: Joao Pereira <[email protected]> Signed-off-by: Ashwin Venkatesh <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Joao Pereira <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
0b80953
to
1551381
Compare
Issues addressed or outdated. Please take another look now.
Signed-off-by: Andrew Meyer <[email protected]>
42ef23c
to
1374c07
Compare
situation where we can pull from remote but the image only exists
locally
[buildpacks/pack#90]