run opencode in "interactive shell" mode

this should resolve any clipboard issues with copying and pasting text

README.md

@@ -9,10 +9,6 @@ The docs below are split into three parts: a **Getting started** walkthrough to
 run it the first time, **How-to guides** for specific tasks, and a **Reference**
 for the moving parts.
 
-> `drc` in the examples is shorthand for `docker compose`
-> (`alias drc='docker compose'`). Substitute `docker compose` if you don't have
-> the alias.
-
 ## Getting started
 
 A first run from a clean checkout.
@@ -114,23 +110,9 @@ networks:
 ```
 
 opencode can then reach it at `http://app:<port>`, where `app` is the **service
-name** from that stack's compose and `<port>` is the container's *internal* port —
-no `ports:` publishing needed.
+name** from that stack's compose and `<port>` is the container's *internal* port.
 
-Note: Bring the opencode stack up first, so `app-opencode_default` exists before adding to your app.
-
-### Executing docker commands from opencode
-The stack runs a dedicated dind (docker in docker) container, and opencode can drive it as a client (`DOCKER_HOST=tcp://dind:2375`). So from inside opencode you can build images, run containers, and `docker compose up` a project's stack. The agent can spin up and test the services it's working on.
-
-A few things that differ from a normal host, because the daemon lives in dind:
-
-- Containers and published ports you start run on the **dind** daemon. Reach a running service at `dind:<port>`, **not** `localhost:<port>`. opencode does not
-  share dind's network namespace, so `localhost` won't reach the stack.
-- The repo needs to be mounted at the same absolute path (`/workspace/repo`) in both the opencode and dind containers, so compose bind-mounts resolve correctly. Work on the checkout there; edits elsewhere won't be visible to the containers dind runs.
-- The dind image store is cached in `./data/dind-cache`, so pulled images stay warm across restarts.
-- To access the services from the host machine, you will need to connect to the dind container or publish the necessary ports from the dind container to your host.
-
-> Note: Opencode itself doesn't run in a privileged container so it can't do privileged actions directly, but it can use the docker daemon in dind to do the same things. Because dind is privileged and in the host user namespace, a container started inside dind can mount the host's raw disk devices and reach the **entire** host filesystem, not only what you shared. This needs opencode to actively do it, but it's a well-known technique, not a theoretical edge case.
+> Note: Bring the opencode stack up first, so `app-opencode_default` exists before adding to your app.
 
 ## Reference
 

docker-compose.yml

@@ -1,30 +1,8 @@
 services:
   opencode:
-    image: redpencil/opencode:feature-with-docker
+    image: redpencil/opencode:0.0.1
+    stdin_open: true
+    tty: true
     volumes:
       - ./data/opencode/share:/root/.local/share/opencode
       - ./config/opencode/opencode.json:/root/.config/opencode/opencode.json
-#      - ./config/opencode:/root/.config/opencode
-    depends_on:
-      dind:
-        condition: service_healthy
-    environment:
-      DOCKER_HOST: "tcp://dind:2375"
-
-  dind:
-    image: docker:29.6-dind
-    privileged: true
-    # userns mode only required if you use user namespaces
-    userns_mode: "host"
-    environment:
-      DOCKER_TLS_CERTDIR: ""
-    volumes:
-      - ./data/dind-cache:/var/lib/docker
-    command:
-      - "--registry-mirror=https://docker-registry-mirror.redpencil.io"
-    healthcheck:
-      test: ["CMD", "docker", "info"]
-      interval: 5s
-      timeout: 3s
-      retries: 20
-      start_period: 10s