Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
boundless-angle-56560
10/14/2021, 2:56 PMHello, I'd like to ask if its possible to somehow optimize Pulumi running time when using Docker images. It seems that pulumi rebuilds images even when there is no change to the image in the sources. Also it seems to me that it doesn't happen always. Sometimes Pulumi happily skips this phase
l
little-summer-88406
10/14/2021, 3:00 PMThis is Docker responsibility I think unless Pulumi is forcing a rebuild, perhaps you do a COPY ./ in the same directory you are make changes to your Pulumi. If docker build takes time then Pulumi will take time. If Docker build is smart enough to detect nothing has changed then I presume Pulumi will gain this benefit too
This means having the layers cached though if on a CI/CD box
b
boundless-angle-56560
10/14/2021, 3:49 PMok I'though that Pulumi wouldn't contact Docker daemon at all if there were no changes to the sources
like, it seems that pulumi is "offloading" the responsiblity to perform the diff to the docker
and everytime a run pulumi I get this:
it tries to push images although there were no changes
😵 1
q
quick-fall-21011
01/16/2022, 11:57 PMI'm having the same issue
Did you ever get a fix for this?