Skip to content

fix(sandbox): percolate no-net param to inform seccomp block - #3348

Merged
agmontem-devel merged 1 commit into
devfrom
namespace-sandbox-network-flag
Nov 19, 2026
Merged

agmontem-devel merged 1 commit into
devfrom
namespace-sandbox-network-flag

Conversation

@agmontem-devel

Copy link
Copy Markdown
Contributor

Description

When using SANDBOX_MODE=NAMESPACE it was observed that, regardless of the presence/omission of --no-net argument, the sandbox_launcher.py blocked network access to user processes. It was desired to conditionally allow such network access.

Changes Made

Forward the no-net parameter state further into the launcher's handlers to not restrict_inet when present.

How to Test

Enable SANDBOX_MODE=NAMESPACE and SANDBOX_ALLOW_NETWORK=TRUE, attempt to run a python request to a network resource (e.g.import requests;requests.get("https://google.com");), confirm <Response [200]> instead of Failed to resolve 'google.com' ([Errno - 2] Name or service not known)

@agmontem-devel
agmontem-devel requested a review from a team as a code owner November 19, 2026 03:34
@snyk-io

snyk-io Bot commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@agmontem-devel
agmontem-devel merged commit 5826aa8 into dev Nov 19, 2026
5 checks passed
@agmontem-devel
agmontem-devel deleted the namespace-sandbox-network-flag branch November 19, 2026 03:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant