fix: add missing Docker image pulls to robustness test workflow #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jiaxiao (mossaka) Zhou <duibao55328@gmail.com>
Signed-off-by: Jiaxiao (mossaka) Zhou <duibao55328@gmail.com>
… CLI, Docker manager, and host iptables Signed-off-by: Jiaxiao (mossaka) Zhou <duibao55328@gmail.com>
…ions workflow Signed-off-by: Jiaxiao (mossaka) Zhou <duibao55328@gmail.com>
…kflow - Add squid:latest and copilot:latest images to pre-pull step in test-firewall-robustness.yml - Configure Squid container to use external DNS servers (8.8.8.8, 8.8.4.4) instead of Docker's embedded DNS - Add DNS configuration to Squid service in docker-compose.yml - Configure squid.conf to use external DNS servers directly - Add security_opt to Squid container to allow UDP DNS queries This addresses timeout issues in the robustness test where containers couldn't be pulled in time and Squid DNS resolution failures. Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
- Add CAP_NET_RAW capability to Squid container to potentially allow UDP DNS operations - This is an experimental fix for "Operation not permitted" errors when Squid tries to send UDP DNS queries Note: This issue appears to be specific to Squid's internal DNS client in Docker containers. Standard tools like nslookup work fine in the same container, suggesting a Squid-specific limitation. Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Contributor
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Add integration test for firewall robustness
fix: add missing Docker image pulls to robustness test workflow
Oct 24, 2025
17 tasks
4 tasks
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The robustness integration test was timing out because the workflow didn't pre-pull the awf Docker images before running tests, causing 30s+ pull delays during test execution.
Changes
Workflow Fix
ghcr.io/githubnext/gh-aw-firewall/squid:latestandghcr.io/githubnext/gh-aw-firewall/copilot:latestto image pre-pull step in.github/workflows/test-firewall-robustness.ymlDNS Configuration
8.8.8.8,8.8.4.4) anddns_search: []to bypass Docker's embedded DNSsquid.confto use external DNS servers directlyCAP_NET_RAWcapability to Squid containerKnown Issue
After fixing the timeout, Squid's internal DNS client fails with "Operation not permitted" when sending UDP queries. System tools (
nslookup) work fine in the same container, suggesting this is specific to Squid's DNS resolver implementation interacting with Docker networking. Investigation ongoing.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.