search

hashicorp / terraform-provider-docker

As part of our introduction to self-service publishing in the Terraform Registry, this copy of the provider has been archived, and ownership has been transferred to active maintainers in the community. Please see the new location on the Terraform Registry: https://registry.terraform.io/providers/kreuzwerker/docker/latest
https://registry.terraform.io/providers/kreuzwerker/docker/latest
Mozilla Public License 2.0
132 stars 92 forks source link

Getting registry information without `host` running docker daemon (such as on terraform Cloud / Enterprise) #227

Closed dvcrn closed 4 years ago

dvcrn commented 4 years ago

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Terraform v0.12.16

Affected Resource(s)

Please list the resources as a list, for example:

I recently migrated to Terraform Cloud and am running into some problems with the docker provider, more specifically that Terraform Cloud / Enterprise doesn't have a docker daemon running locally. I am using the docker provider to fetch image tags from a private registry, to update other resources such as kubernetes if necessary.

My question is, is it possible to fetch docker information (such a tags and hashes) without using a daemon? Or are there plans to provide a daemon in Terraform Cloud?

mavogel commented 4 years ago

My question is, is it possible to fetch docker information (such a tags and hashes) without using a daemon? Or are there plans to provide a daemon in Terraform Cloud?

Sorry @dvcrn I cannot answer this question, but maybe one of the core team like @radeksimko can.

radeksimko commented 4 years ago

I don't believe there are any public plans to run any such daemons in Terraform Cloud, but it may be best to direct any questions related to Terraform Cloud or Terraform Enterprise to our official support channels.

The important question is what do you mean by "private registry". Is it just publicly available registry which requires users to be authenticated & authorized, or is it entirely "firewalled-off" from the internet?

In the former case you should be able to work with it from anywhere (including TFC/TFE), assuming you provide correct authentication to the provider.

The latter case boils down to a few much more generic questions (unrelated to Docker provider) with potentially more complex answers:

Depending on your answers to the above, one of the possible solutions may also be TFE - which is self-hosted solution that can run in your own network.

But again - I may not be familiar with all the details and current functionality TFC or TFE offers today or the roadmap of either. Filling a support ticket is therefore the best way forward as you will get the most accurate answer.

dvcrn commented 4 years ago

@radeksimko I missed your response - sorry!

I meant it is a public registry, but requires users t be authenticated.

In the former case you should be able to work with it from anywhere (including TFC/TFE), assuming you provide correct authentication to the provider.

The problem for this is still that this provider requires the host key which should point to a docker daemon/client to be used to connect to the registry. Terraform Cloud/Enterprise doesn't have a docker client, so this provider can't be used.

There are some hacks over here, but it would be much nicer if this provider could just connect to those registries to at least query image tags and metadata through the docker API.