-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no port found in cookbook url - can't download cookbooks unless listening on port 80 #5
Comments
That's weird, what version of chef are you running? This isn't happening for me (I can download cookbooks). |
|
@jkeiser it might be worth noting that the URL comes back without a port on my end. This doesn't you can't download them, it just means that if you don't inject the port into the URL coming back from the sandbox that you wont' be able to download it |
@jkeiser confirming this |
After much fun, we figured out Ridley was sending the wrong port: berkshelf/ridley#139 Thanks @sethvargo for helping find the issue and @reset for fixing it :) |
After uploading a cookbook to the ChefZero server the URL of each cookbook file does not contain the port of the running ChefZero server.
This means that when you attempt to download the cookbook, unless you started ChefZero on port 80, you'll receive a connection error.
Here's the "resources" collection of a cookbook in the ChefZero server:
You'll notice that the url is
http://localhost/file_store/b70ba735f3af47e5d6fc71b91775b34c
but the ChefZero server is actually running on 8889The text was updated successfully, but these errors were encountered: