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
I have a use-case where I want to leverage the docker_registry_image data sources in an environment where I don't have access to a Docker daemon but want to be able to validate that an image exists in a registry and fetch details of that image.
Currently this error comes back:
Error: Error pinging Docker server: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Would ideally like a way to disable needing access to the Docker daemon so I can still use resources that do not require it.
Potential Terraform Configuration
# Copy-paste your Terraform configurations here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file. For# security, you can also encrypt the files using our GPG public key.provider"docker" {
disable_docker_daemon_check=true|false# default: falseregistry_auth {
address="registry-1.docker.io"
}
}
The text was updated successfully, but these errors were encountered:
Community Note
Description
I have a use-case where I want to leverage the
docker_registry_image
data sources in an environment where I don't have access to a Docker daemon but want to be able to validate that an image exists in a registry and fetch details of that image.Currently this error comes back:
Would ideally like a way to disable needing access to the Docker daemon so I can still use resources that do not require it.
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: