Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Add support for chef-provisioning-docker #329

Closed
drazzib opened this issue Mar 2, 2015 · 8 comments
Closed

Add support for chef-provisioning-docker #329

drazzib opened this issue Mar 2, 2015 · 8 comments
Labels
Type: Enhancement Adds new functionality.

Comments

@drazzib
Copy link

drazzib commented Mar 2, 2015

Hi,

I notice that many chef-provisioning-* providers are already packaged into Chef DK but chef-provisioning-docker seems to be missing.

I'd like to request inclusion of Docker provider so that I can use Chef DK for quick local testing.

Regards,

@kramvan1
Copy link

kramvan1 commented Mar 2, 2015

👍 Yes, would also like to see docker in the DK

@danielsdeleo
Copy link
Contributor

This is managed by omnibus-chef, you can look here for examples and file a pull request with that project. If the dependencies aren't too bad it should be pretty easy: https://github.com/chef/omnibus-chef/tree/master/config/software

@acqant
Copy link

acqant commented May 1, 2015

Would that keep chef-provisioning-docker in step with chefDK/chef-provisioning? It's not a good first impression when chefDK ships a chef-provisioning version that then doesn't have a working provisioner.

@danielsdeleo
Copy link
Contributor

It's not a good first impression when chefDK ships a chef-provisioning version that then doesn't have a working provisioner.

What do you mean by this? ChefDK ships with AWS, Fog, Azure, and Vagrant. Is there a bug? Or is it just that docker is the only one you care about?

@acqant
Copy link

acqant commented May 1, 2015

I can make do with vagrant for now but was hoping to deploy to production
with both Hanlon/crowbar and docker.
On May 1, 2015 5:24 PM, "Dan DeLeo" notifications@github.com wrote:

It's not a good first impression when chefDK ships a chef-provisioning
version that then doesn't have a working provisioner.

What do you mean by this? ChefDK ships with AWS, Fog, Azure, and Vagrant.
Is there a bug? Or is it just that docker is the only one you care about?


Reply to this email directly or view it on GitHub
#329 (comment).

@acqant
Copy link

acqant commented May 2, 2015

I just had an expectation that what was documented as working in the chef-provisioning repo would all work within chefDK. This isn't chefDK's problem obviously.

It seems care was taken to get AWS, FOG and other drivers working with a 1.x version of chef-provisioning but the others seem to be left behind. A note in the Readme.md of chef-provisioning about what does and doesn't work with 1.x would help. I'll see who I can find over their.

@danielsdeleo
Copy link
Contributor

You should be able to install whatever other provisioning drivers you need with chef gem install. As for what's included by default, that's always a thorny question but I could see there being a case for including the docker stuff.

@charlesjohnson
Copy link
Contributor

Closing this for now. If we decide we need to revisit the provisioning drivers that ship with Chef-DK, we can re-open.

@thommay thommay added Type: Enhancement Adds new functionality. and removed Enhancement labels Feb 1, 2017
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Enhancement Adds new functionality.
Development

No branches or pull requests

6 participants