feat: enable Docker CLI inside container image #11
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.
✨ Summary
Enable Docker CLI and Compose v2 inside the
codex-universal
container image for Ubuntu 24.04 by installing thedocker.io
client plus thedocker-compose-v2
plugin in a dedicated ### DOCKER ### layer.This guarantees
docker compose …
works out‑of‑the‑box when Codex tests repositories that rely on container orchestration.Fixes #10
🔍 Context
docker compose
.docker.io
does not bundle Compose—the v2 CLI lives indocker-compose-v2
. Installing both packages (no daemon, just CLI) unblocks container workflows while keeping the existing security model (CLI talks to a mounted socket; no privileged service starts inside the image).🛠️ What’s inside
Dockerfile
apt-get install -y --no-install-recommends docker.io docker-compose-v2
in a new ### DOCKER ### layerNo other files or behaviours are modified.
🚀 How to Test
Optional smoke‑test
All commands should succeed without “command not found” errors.
📏 Impact & Size
📝 Checklist
docker.io
+docker-compose-v2
installed in Dockerfiledocker compose
verified inside rebuilt image