-
Notifications
You must be signed in to change notification settings - Fork 40
In fresh container : /etc/chef/client.pem: no such file or directory #35
Comments
Check your docker service API version ( |
I'm currently using this version :
The calls on the docker-api are done on the 1.16 version of the API and it seems to be working properly ... |
I've just tried to run it myself. Works fine for me. Though my chef-client version is 11.18.6 (had pain with >=12.0.0) and I also use chef-provisioning v0.19 (anything >=v0.20 is not supported yet). |
What is surprising to me is that the docker log is showing an attempt to write the file etc/chef/client.pem without the first / Here are the debug log of the chef client
Is the issue is the "Unsupported platform" ? |
Ok I got it here is the super hack I had to do:
Well, that makes me a bit sad as now it move forward, but I'm stuck at this point:
I can't have a proxy set to connect to docker but I need to proxy to connect to chef.io. |
It looks very similar to this issue: tmatilai/vagrant-proxyconf#109 |
As stated in the following documentation, Docker cli will honour the proxy set in the environment which is also true for the NO_PROXY variable : icecrime/docker@3a1dbef I'm not able to run the chef-client as expected with the following:
I guess that's more of a Docker issue then, I'm closing this. |
Hey all,
I'm using the unedited web_server example in the README.md of this repo.
The chef-client is ending with the following error :
The docker logs are showing that the container is properly created, the chef-client is trying to create the key in /etc/chef/client.pem but the file is apparently not properly created as you can see in the following docker logs:
chef-client output :
The text was updated successfully, but these errors were encountered: