Bug

The Presto docker-compose file (tools/deployment/presto-clp/docker-compose.yaml) uses mutable
:dev image tags for both presto-coordinator and presto-worker services without setting
pull_policy: "always". Docker Compose's default pull policy is missing, which means it only
pulls an image if one doesn't already exist locally. As a result, once a :dev image is cached
locally, subsequent docker compose up invocations will reuse the stale local copy even if a newer
version has been pushed to the registry.

Expected: Running docker compose up should always use the latest :dev images from the
registry.

Actual: Docker reuses the locally cached :dev images, which may be outdated.

Affected services:

• presto-coordinator: ghcr.io/y-scope/presto/coordinator:dev
• presto-worker: ghcr.io/y-scope/presto/prestissimo-worker:dev

CLP version

dbc1799

Environment

Any environment using Docker Compose with the Presto deployment (tools/deployment/presto-clp/docker-compose.yaml) that has previously pulled an older Presto image.

Reproduction steps

1. Run docker compose up in tools/deployment/presto-clp/ to pull the :dev images.
2. Wait for a newer :dev image to be pushed to the registry.
3. Run docker compose up again.
4. Observe that the locally cached (stale) images are used instead of the latest ones from the
   registry.