Skip to content

Preinstall Docker CLI and Docker Compose in dev images (REMOTE-2140)#20

Open
seemeroland wants to merge 2 commits into
mainfrom
oz-agent/REMOTE-2140-docker-compose-in-dev-images
Open

Preinstall Docker CLI and Docker Compose in dev images (REMOTE-2140)#20
seemeroland wants to merge 2 commits into
mainfrom
oz-agent/REMOTE-2140-docker-compose-in-dev-images

Conversation

@seemeroland

Copy link
Copy Markdown

Summary

Preinstalls the Docker client tools in every warpdotdev/dev-* image so docker, docker compose, and the standalone docker-compose command are ready to use out of the box in Warp hosted sandboxes.

This resolves REMOTE-2140: customers running Docker Compose–based workflows in Warp hosted sandboxes previously had to install Docker/Compose themselves via setup commands (or maintain a custom image). Now the tooling ships in the regular images.

What changed

  • Dockerfile: New INSTALL_DOCKER build arg (defaults to true) that installs:

    • docker CLI (extracted from Docker's static binary bundle)
    • Compose v2, available as both docker compose and docker-compose
    • Buildx (docker buildx, used by docker compose build)

    Pinned versions, linux/amd64 + linux/arm64 support. Build with --build-arg INSTALL_DOCKER=false for a slimmer image.

  • README: New "Docker & Docker Compose" section documenting the preinstalled tooling and clarifying that only the client tools are installed — a Docker daemon is provided by the sandbox host at runtime (e.g. Docker-routed sandboxes).

Because the tooling is installed by default and the build workflow does not override INSTALL_DOCKER, all published images (base, all language variants, and their -agents variants) get Docker + Compose.

Validation

  • Confirmed all download URLs (docker static bundle, compose plugin, buildx) return 200 for both x86_64/amd64 and aarch64/arm64.
  • Verified the tar --strip-components=1 ... docker/docker extraction places the docker CLI binary at the expected path.
  • Version-check commands run at build time and do not require a daemon.

Note: a full multi-arch image build was not run in this environment (no Docker daemon available); CI's build-images workflow will build and push on merge.

Conversation: https://staging.warp.dev/conversation/8648ade1-c0f7-42af-a79e-235096d1d9e5
Run: https://oz.staging.warp.dev/runs/019f5cde-14b4-7648-ac55-bf2a72900a3b

This PR was generated with Oz.

Adds the Docker client tools (docker CLI, Compose v2 plugin, and Buildx) to
every published dev image so `docker`, `docker compose`, and the standalone
`docker-compose` command are ready to use out of the box. This removes the need
for customers to install Docker via setup commands to run Docker Compose–based
workflows in Warp hosted sandboxes.

- Installed by default via a new INSTALL_DOCKER build arg (defaults to true),
  overridable with --build-arg INSTALL_DOCKER=false for slimmer images.
- Uses pinned static binaries for the docker CLI, compose plugin, and buildx,
  supporting both linux/amd64 and linux/arm64.
- Only client tools are installed; a Docker daemon is provided by the sandbox
  host at runtime.

Co-Authored-By: Oz <oz-agent@warp.dev>
@seemeroland seemeroland added the from-feedback-bot Delegated from the Feedback Bot label Jul 13, 2026 — with Warp Dev Github Integration
@bnavetta
bnavetta marked this pull request as ready for review July 15, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

from-feedback-bot Delegated from the Feedback Bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants