Skip to content
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

Image build cacheFrom property does not match Docker CLI functionality #127

Closed
bob-bins opened this issue Jan 19, 2020 · 1 comment
Closed
Assignees
Labels
4.x.x kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone

Comments

@bob-bins
Copy link

Docker CLI allows you to specify another image to use as the cache source. Pulumi only allows you to use the same image that you're building as a cache source. This is problematic if one wants their images to be immutable. It would be great if you could also specify an arbitrary image as the cache source in Pulumi.

Docker CLI:
--cache-from Images to consider as cache sources

npm @pulumi/[email protected]:

/**
 * An optional CacheFrom object with information about the build stages to use for the Docker
 * build cache. This parameter maps to the --cache-from argument to the Docker CLI. If this
 * parameter is `true`, only the final image will be pulled and passed to --cache-from; if it is
 * a CacheFrom object, the stages named therein will also be pulled and passed to --cache-from.
 */
cacheFrom?: pulumi.Input<boolean | CacheFrom>;
@infin8x infin8x added kind/enhancement Improvements or new features and removed enhancement labels Jul 10, 2021
@AaronFriel AaronFriel added this to the 0.85 milestone Feb 13, 2023
@guineveresaenger guineveresaenger added the resolution/fixed This issue was fixed label Feb 16, 2023
@guineveresaenger
Copy link
Contributor

This is fixed via #500 and #467.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x.x kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

5 participants