cuddly-leather-18640
06/16/2021, 7:17 PMcache-from
feature of the pulumi docker go implementation is broken: https://github.com/pulumi/pulumi-docker/issues/238
I can hack around this by:
1. pulling the image I want to use as a cache
2. manually running docker build --cache-from my-image
3. executing `pulumi preview`/`pulumi up`
My intuition tells me that the manual docker build
step should populate the layer cache and therefore speed up the pulumi commands which build the docker image but I’m finding that even with this workflow pulumi recreates the docker image from scratch.
Is my intuition incorrect? If so how? Is there another way I can hack around the current bug with cache-from in the go implementation?bored-activity-40468
06/16/2021, 9:29 PMcuddly-leather-18640
06/17/2021, 2:38 PMList<string>
and go doesn’t have genericsbored-activity-40468
06/17/2021, 3:03 PMcuddly-leather-18640
06/17/2021, 3:29 PMDOCKER_BUILDKIT
and it’s inline cacheCacheFrom
for go is broken - is the CacheFrom for your example critical for caching to work?bored-activity-40468
06/17/2021, 3:52 PMcuddly-leather-18640
06/17/2021, 5:15 PMbored-activity-40468
06/17/2021, 6:00 PMcuddly-leather-18640
06/17/2021, 7:37 PMDOCKER_BUILDKIT
and use BUILDKIT_INLINE_CACHE
and skip using CacheFrom
entirely.