Closed ninjatux closed 9 years ago
Hi @NinjaTux
It appears that cloudbees is already running nginx or the base image you are using already has the port bound for some reason (perhaps cloudbees is using it for something else). Unfortunately we are not experts in Jenkins or Chef, so it is difficult to reproduce this issue. If you are able to identify a specific Packer issue, we would be happy to fix it :smile:.
You might also try asking this question on the mailing list to see if anyone from the Packer community has experienced the same issue.
Thanks @sethvargo, for now we solved this with a workaround :)
When we execute
packer build
locally withchef_solo
everything works as expected, theamazon-ebs
builder uses chef to provision the machine and then packer creates the image.However when we run the same code on Jenkins (hosted on Cloudbees) we have problems as you can see in the logs:
Does anyone experienced the same issue? How I can achieve an automate image generation otherwise using Jenkins?