-
Notifications
You must be signed in to change notification settings - Fork 14
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
Allow using Docker images that are already built locally #835
Comments
Hi @rlukata Could you please provide a little bit more details about your idea? What is the main motivation to do so? Can you describe a use case where you would expect this to work? I expect there may be some difficulties in understanding whether a local image can be reused or not in all cases, but maybe you have a very specific scenario in mind? |
We heavily use S3 caching (cache-to and cahce-from) in CI, and since the I think that it would greatly simplify the orchestration and would be an elegant way to manage resource dependencies/relationships if I could build the images outside of pulumi -to leverage the ever-changing buildx features, and then use pulumi to push/deploy these images. |
Hi @rlukata, we just released a new Docker Build provider focused exclusively on building images with buildx/BuildKit. It should provide all of the buildx features you need, and we recommend you use it for building images going forward. Please take a look and give us feedback! The repository is here; our blog announcement is here; and finally API docs are here along with examples of how to migrate your existing We won't be able to add this functionality in this provider for a number of reasons, so I'm closing this as wont-fix. |
Hello!
Issue details
When using
new docker.Image
, check if there's an are already built image locally instead of having to rebuild them.Affected area/feature
Docker
The text was updated successfully, but these errors were encountered: