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
I just tested it. The creation did work for me, but running terraform destroy resulted in an error.
Internally we are using only the name to identify the image and retrieve its information. In your case we have the same name with two tags => our code gets confused.
I think I was just lucky that the creation worked...
You can also test it yourself: docker inspect build-python3.9-openssl should output Error: No such object.
It actually works if you append the tag also to the name: name = "build-python3.9-openssl:latest-arm64" because then it uses the full image identifier when communicating with the docker daemon
Here's my Terraform:
And here's the images that get created:
Yet for some reason,
docker_image.x86_64
is pointing to theimage_id
ofdocker_image.arm64
, which is definitely wrong.Results in:
My guess at the moment is that somewhere in this provider it's grabbing
latest
and using that forimage_id
, but I have not dug much into this.The text was updated successfully, but these errors were encountered: