You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far I have a docker_registry_image with a build statement set to a path where I generate a Dockerfile.
My generated Dockerfile only includes a FROM statement set to the image from the source registry
The problem is the build context is altered as part of the first run and then I need to run Terraform twice. This isn't so nice for my users, as the image is always rewritten and each Terraform run needs to rebuild my image. For now I checked the current source image in to git, to avoid that error in the first run, but I'd like to avoid that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So far I have a docker_registry_image with a build statement set to a path where I generate a Dockerfile.
My generated Dockerfile only includes a FROM statement set to the image from the source registry
The problem is the build context is altered as part of the first run and then I need to run Terraform twice. This isn't so nice for my users, as the image is always rewritten and each Terraform run needs to rebuild my image. For now I checked the current source image in to git, to avoid that error in the first run, but I'd like to avoid that.
Is there any better way to do this?
Here's what my code looks like:
LeanerCloud/terraform-aws-autospotting@d9ad5d0#diff-44cedb7989fb5db19755e1558d23537a04fef1839263fd123b246e7ce3eb5a89
Beta Was this translation helpful? Give feedback.
All reactions