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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Docker supports creating multi-platform images using docker buildx. This generates per-architecture images that are untagged and a manifest list image that points to the others and gets labeled and tagged. The existing docker_registry_image data source is not able to handle these effectively. However, it is useful to be able to query information about the underlying images for cases that do not currently support multi-arch images (AWS Lambda for example).
It seems like the right way to handle this is to create a new data source that handles multi-arch images.
New or Affected Resource(s)
docker_registry_multiarch_image - A new data source that allows reading multi-arch images.
Potential Terraform Configuration
data"docker_registry_multiarch_image""list" {
name ="alpine:latest"
}
References
Support for Docker buildx聽#417 - Somewhat related as these images are created using docker buildx. However, 417 is for the write side and this issue is for the read side.
The text was updated successfully, but these errors were encountered:
I have implemented this in #565. If you read the alpine:latest image as in the Potential Terraform Configuration section above, the resulting data object looks like this:
Community Note
Description
Docker supports creating multi-platform images using
docker buildx
. This generates per-architecture images that are untagged and a manifest list image that points to the others and gets labeled and tagged. The existingdocker_registry_image
data source is not able to handle these effectively. However, it is useful to be able to query information about the underlying images for cases that do not currently support multi-arch images (AWS Lambda for example).It seems like the right way to handle this is to create a new data source that handles multi-arch images.
New or Affected Resource(s)
Potential Terraform Configuration
References
docker buildx
. However, 417 is for the write side and this issue is for the read side.The text was updated successfully, but these errors were encountered: