revert: remove docker-wrapper (docker-in-docker not supported)

[Copilot]

This PR reverts the docker-wrapper implementation as Docker-in-Docker support was intentionally removed in v0.9.1 (PR #205). Running docker run inside the agent container is not a supported use case in the current AWF architecture.

Changes Reverted

All changes from the original implementation have been reverted:

• Removed containers/agent/docker-wrapper.sh - Docker wrapper script that was created to inject --add-host flags
• Reverted containers/agent/Dockerfile - Removed docker-wrapper installation
• Reverted containers/agent/entrypoint.sh - Removed AWF_ENABLE_HOST_ACCESS readonly declaration
• Reverted src/docker-manager.ts - Removed AWF_ENABLE_HOST_ACCESS environment variable passing
• Reverted src/docker-manager.test.ts - Removed tests for AWF_ENABLE_HOST_ACCESS

Rationale

The original feature request was based on a misunderstanding of the AWF architecture. Docker-in-Docker was intentionally removed to:

• Prevent security vulnerabilities associated with Docker socket mounting
• Simplify the container security model
• Align with the design decision documented in PR feat: remove Docker-in-Docker support #205

The agent container is designed to work without Docker commands available, and spawning containers from within the agent is not supported.

Status

This PR should be closed as the requested feature conflicts with the intentional removal of Docker-in-Docker support.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature] Propagate host.docker.internal DNS to spawned containers</issue_title>
<issue_description>## Background

PR #210 proposed configuring Docker's /etc/hosts when --enable-host-access is used, so spawned containers can resolve host.docker.internal.

Problem

When --enable-host-access is used, spawned containers via docker-wrapper need host.docker.internal DNS resolution.

Proposed Changes

1. Pass AWF_ENABLE_HOST_ACCESS environment variable to agent container
2. Modify docker-wrapper.sh to:
   • Allow --add-host host.docker.internal:host-gateway specifically when AWF_ENABLE_HOST_ACCESS=true
   • Inject --add-host host.docker.internal:host-gateway to spawned containers when enabled
3. Security fix: Make AWF_ENABLE_HOST_ACCESS readonly in entrypoint.sh to prevent malicious code from tampering with the variable

Security Note

The environment variable should be declared readonly in entrypoint.sh, preventing malicious code from enabling host access when it wasn't authorized.

---

Issue created from PR #210 during backlog cleanup</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature] Propagate host.docker.internal DNS to spawned containers #422

---

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

[Mossaka]

@copilot close this PR since docker run inside the agent is not possible

[Copilot]

@copilot close this PR since docker run inside the agent is not possible

You're correct. Docker-in-Docker support was removed in v0.9.1 (PR #205), so spawning containers via docker run inside the agent is not supported.

I've reverted all the changes in commit cafa228. The PR is now ready to be closed.