Skip to content
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

Closed
nickcharlton opened this issue Aug 17, 2013 · 6 comments
Closed

Firewall collisions on OS X. #303

nickcharlton opened this issue Aug 17, 2013 · 6 comments

Comments

@nickcharlton
Copy link

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:

  • Building a Ubuntu box: preseed.cfg isn't provided, so goes straight to user configuration.
  • When using the Vagrant post processor, Packer never finishes, leaving you with:
==> Builds finished. The artifacts of successful builds are:

but not actually presenting the results, or exiting.

All of these can be solved by either:

  1. Turning off the firewall.
  2. Adding exceptions for the packer binaries.

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

@mitchellh
Copy link
Contributor

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.

@nickcharlton
Copy link
Author

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 packer-builder-virtualbox). Then it will generate the box fine, but not exit.

@mitchellh
Copy link
Contributor

Thanks, that is super weird. I'll have to dig into this more to see if I reproduce. Thanks.

@mitchellh
Copy link
Contributor

I can't reproduce this :( Are you able to reproduce issues with basic commands like packer (which uses TCP sockets underneath to talk to subprocesses). Otherwise, can you just give me a set of steps to get this to work?

Sorry.

I'm going to close this for now while I gather more information, I'll continue to get emailnotifications if it changes.

@nickcharlton
Copy link
Author

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!

@mitchellh
Copy link
Contributor

Great!

@ghost ghost locked and limited conversation to collaborators Apr 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants