-
Notifications
You must be signed in to change notification settings - Fork 64
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
BITS (Background Intelligent Transfer Service) wants to set firewall settings but can't in a container #354
Comments
I'm still interested in discussing this. Any ideas @npolito-msft? |
@fady-azmy-msft is @npolito-msft an active person? This thread seems dead. |
This issue has been open for 30 days with no updates. |
5 similar comments
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
3 similar comments
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
@borhae I'm going to triage this again. |
BITS requires network access which means it needs to set firewall rules. However, the Windows Firewall does not run inside a container so any calls will fail. You won't be able to use BITS to transfer files. The good news is that our product team is aware of this request and I'll update this Issue when we have something to share. |
Thank you so much for the response, I was already assuming that this issue is completely out of scope of what windows containers are meant to be useful for. I'm still interested in any outcome of this. |
I'm going to close this Issue for now but I'll reopen + update it when we have news to share. |
I wanted to evaluate a distributed, peer to peer, install scenario with windows containers. BITS by Microsoft seemed like a good choice, to distribute installation packages. When trying to configure the windows containers to enable the peer to peer install I ran into issues detailed below.
I know, that windows containers don't come with a firewall, because the host systems firewall is used. But BITS wants to change firewall settings on the system it is running (understandably) and doesn't even know that there is an external one (where a configuration wouldn't make sense anyway).
Question: How can I enable Peer 2 Peer mode for BITS inside a container?
What I tried:
Executing
inside the windows docker container via powershell, As a result I get the following error:
I found some instructions that indicated that I should try to check whether the firewall is running by:
But as a result I get:
When I try to start the firewall by
I get the following error:
The text was updated successfully, but these errors were encountered: