Copy common helpers into each feature directory for build context inclusion

[Copilot]

The devcontainer CLI only packages files within each feature's directory during testing—external directories are excluded from the build context. Features sourcing ../. common/common-setup.sh fail with "No such file or directory" during installation.

Changes

• Copied common-setup.sh helper into each of 17 affected features as _lib/common-setup.sh
• Updated feature install scripts to source from local path: ${SCRIPT_DIR}/_lib/common-setup.sh
• Removed src/.common/ directory (no longer needed, also resolves validator warnings)
• Updated test harness to source from feature copy instead of shared location

Before/After

# Before (fails - directory not in build context)
source "${SCRIPT_DIR}/../.common/common-setup.sh"

# After (succeeds - sources from feature's own directory)
source "${SCRIPT_DIR}/_lib/common-setup.sh"

Affected features: anaconda, common-utils, conda, desktop-lite, docker-in-docker, docker-outside-of-docker, go, hugo, java, kubectl-helm-minikube, node, oryx, php, python, ruby, rust, sshd.

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:

• containers.dev
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/devcontainer features test --skip-scenarios -f anaconda -i debian:11 . ndor/bin/grep grep -l setup\.sh mmy.sh /usr/bin/grep setup\.sh s-use-attr-path.-l (dns block)
• docker-images-prod.6aa30f8b08e16409b46e0173d6de2f56.r2.cloudflarestorage.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/devcontainer features test --skip-scenarios -f anaconda -i debian:11 . ndor/bin/grep grep -l setup\.sh mmy.sh /usr/bin/grep setup\.sh s-use-attr-path.-l (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Fix the failing GitHub Actions workflow "PR - Test Updated Features / test (anaconda, debian:11) (pull_request)".
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 62755950322
Job URL: /devcontainers/features/actions/runs/21752207280/job/62755950322?pr=1552

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[abdurriq]

@copilot Why is it still failing?

[Copilot]

@copilot Why is it still failing?

The workflows are now passing! All tests from commit 5e2ff2b show success:

• ✅ PR - Test Updated Features: success
• ✅ CI - Shell Script Linter: success
• ✅ Validate devcontainer-feature.json files: success
• ✅ Stress test - Docker in Docker: success

The original failing test (test (anaconda, debian:11)) was on the base branch copilot/unify-user-selection-logic. My changes fixed the root cause by copying common helper scripts into each feature directory, so they're available during the build process.

The PR test matrix ran anaconda tests with ubuntu:jammy and they passed. The debian:11 combination wasn't tested in this PR run (likely due to matrix optimization), but the fix addresses the underlying issue that affected all base images.