-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Firewall collisions on OS X. #303
Comments
Can you get me a debug log for this? Packer uses a LOT of TCP localhost bound TCP connections, so you need to allow it. But if you deny it, it should properly fail. Unsure why it is continuing. |
Yep, here we go: http://git.io/jY2zWA It took a bit of a while to replicate again reliably (you need to reload the Firewall daemon after changing allowed/blocked settings). So, to confirm: This is run with the Firewall on, but no Packer related exceptions. Packer will cause the Firewall to confirm you wish it to allow incoming connections (but, only on |
Thanks, that is super weird. I'll have to dig into this more to see if I reproduce. Thanks. |
I can't reproduce this :( Are you able to reproduce issues with basic commands like Sorry. I'm going to close this for now while I gather more information, I'll continue to get emailnotifications if it changes. |
I also cannot replicate it – or at least, I cannot replicate this now I've moved to Packer v0.3.4. I'll reopen if I see if from now on, but I guess #313 was indeed related. Thanks! |
Great! |
This seems to cause all manner of funny behaviour with packer because the OS X firewall objects to processes opening sockets without permission.
So, a couple of issues I've seen:
preseed.cfg
isn't provided, so goes straight to user configuration.but not actually presenting the results, or exiting.
All of these can be solved by either:
I'm not sure if this should be Packer's issue to solve, but I think it's worthwhile having documented if others find the same thing. Or, possibly Packer should self test and error out?
Sys Info
The text was updated successfully, but these errors were encountered: