Andrew Beard

My feedback

  1. 167 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  9 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Beard commented  · 

    I've been playing around with installing Project Honolulu within a Windows docker container and it seems like the installer has a dependency on the Windows Firewall:

    MSI (s) (5C:C0) [02:39:38:376]: Created Custom Action Server with PID 2304 (0x900).
    MSI (s) (5C:A8) [02:39:38:407]: Running as a service.
    MSI (s) (5C:A8) [02:39:38:423]: Hello, I'm your 32bit Elevated Non-remapped custom action server.
    ExecFirewallExceptions: Installing firewall exception2 SmeInboundOpenException on port 443, protocol 6
    ExecFirewallExceptions: Error 0x800706d9: failed trying to find existing port rule
    ExecFirewallExceptions: Error 0x800706d9: failed to add/update port exception for name 'SmeInboundOpenException' on port 443, protocol 6
    CustomAction WixExecFirewallExceptionsInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    It looks like the installer insists on trying to open a hole in the firewall for port 443 (the port I specified to msiexec) and since the firewall isn't running on server core containers the install fails. It seems like Project Honolulu is a good fit for running in a container as opposed to a full VM, but this installer issue prevents it from working correctly.

    Andrew Beard supported this idea  · 

Feedback and Knowledge Base