What docker/compose shipped
Written by FoxPlug from the repository's own releases; not affiliated with Docker. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/docker/compose; Docker did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 9, 2026
What shipped
- Released v5.7.1 with OCI manifest verification, consistent OCI cache handling and a Git checkout fix. Release
- Docker compose down -v with a service selection no longer removes volumes still used by other services. Pull request #14449
- The --scale flag now rejects an empty service name instead of accepting it. Pull request #14481
- Compose config --images now skips provider services that declare neither an image nor a build. Pull request #14332
- Fetched OCI manifests are now verified against their digest, and only complete cache entries are used. Pull request #14490
- Remote resource cache is split into a directory per kind, and a Git checkout is kept only once complete. Pull request #14475
- The OCI loader no longer treats a null manifests field as an image index, and reports host directory failures as host failures. Pull request #14491
- Go was updated to 1.27.4, which includes security fixes. Pull request #14489
- Go was updated to 1.27, aligning certificate environment variable handling on Windows and macOS. Pull request #14486
- Golangci-lint was updated to v2.15.0 for Go 1.27 compatibility. Pull request #14487
Why it matters
This week brings a v5.7.1 release and a set of fixes around volumes, scaling and OCI and Git caching that affect how projects are pulled and torn down. Users of down -v with a service selection should see fewer surprises with shared volumes, and the cache fixes make interrupted pulls and concurrent access less likely to leave inconsistent state.
Changelog entry
- Release v5.7.1. Release
- Down -v with services keeps volumes other services use. Pull request #14449
- Scale rejects an empty service name. Pull request #14481
- Config --images skips pure resource provider services. Pull request #14332
- OCI manifests are verified against their digest and only complete cache entries are used. Pull request #14490
- Remote resource cache has one directory per kind and Git checkouts are placed once complete. Pull request #14475
- OCI loader distinguishes a null manifests field and reports host failures as host failures. Pull request #14491
- Update Go to 1.27.4. Pull request #14489
- Update Go to 1.27. Pull request #14486
- Update golangci-lint to v2.15.0. Pull request #14487
- Relay image is built like the compose binary. Pull request #14497
- Reverted the pflag dependency bump. Pull request #14496
Compose v5.7.1 is out. down -v with services no longer removes volumes other services use, --scale rejects empty service names, and OCI manifests are verified against their digest. Plus a split cache for Git and OCI resources and an update to Go 1.27.4.
Compose v5.7.1 is out this week. It brings OCI manifest verification against the requested digest, cache handling that stays consistent on interruption and concurrent access, and a Git checkout that is kept only once complete. docker compose down -v with a service selection no longer removes volumes used by services outside that selection, and the --scale flag now rejects an empty service name. compose config --images skips provider services that declare neither an image nor a build. Remote resource caches now have a directory per kind. The project was updated to Go 1.27.4 with its security fixes.
Week of November 2, 2026
What shipped
- Released v5.7.0, in which up runs its Create and Start phases as a single plan over a single daemon snapshot for up -d and interactive up, while the CLI behaves as before. Release
- Fixed up, create and run reporting networks and volumes twice, so each now shows progress once on its own row. Pull request #14467
- Fixed the cache of extracted OCI projects so an entry is either complete or absent when a run is interrupted or several runs access it at once. Pull request #14462
- Fixed down --rmi local|all so images of services outside the teardown selection are kept. Pull request #14458
- Fixed events --until treating io.EOF from the Engine client as a normal end of the bounded stream instead of an error. Pull request #14444
- Hardened how
use_api_sockethands registry credentials to a service, readable by the container's root only and not injected when the service uses its own Docker config. Pull request #14402 - Moved the warning that uid, gid and mode on service-level configs and secrets references are ignored to container creation, and only when a file source really ignores them. Pull request #14299
- Moved the images command, local image identity and project image pruning into an internal/images package with no change in behavior. Pull request #14406
- Moved logs, attach, the container event monitor and the log printer into an internal/logstream package with no change in behavior. Pull request #14407
- Migrated the first legacy icmd end-to-end tests for events,
env_fileandstart_stopto the declarative Scenario DSL without changing what they verify. Pull request #14414
Why it matters
This week brought v5.7.0, which changes how up runs its Create and Start phases as a single plan while keeping the CLI the same, and notes this matters to people using Compose as a library. It also fixed several user-facing problems: duplicated network and volume progress, images outside the teardown selection being removed by down --rmi, OCI project cache consistency under interruption and concurrent access, and events --until ending with an EOF error.
Changelog entry
- Release v5.7.0: up runs its Create and Start phases as a single plan over a single daemon snapshot for up -d and interactive up; the CLI behaves as before. Release
- Fix networks and volumes being reported twice by up, create and run; progress now shows once on its own row. Pull request #14467
- Keep the cache of extracted OCI projects consistent on interruption and concurrent access: an entry is either complete or not there. Pull request #14462
- Preserve images of services outside the teardown selection when running down --rmi local|all. Pull request #14458
- Treat io.EOF as a normal end of a bounded stream so events --until no longer reports an error at its deadline. Pull request #14444
- Harden the credentials handed to a service by
use_api_socketto align with docker run --use-api-socket. Pull request #14402 - Warn about ignored uid, gid and mode on service-level configs and secrets references at container creation, and only when a file source ignores them. Pull request #14299
- Move images and image pruning to internal/images with no behavior change. Pull request #14406
- Move logs and attach to internal/logstream with no behavior change. Pull request #14407
- Move the service dependency graph to internal/depgraph. Pull request #14410
- Migrate the first legacy icmd end-to-end tests to the Scenario DSL without changing what they verify. Pull request #14414
- Add tests locking the behaviors of the start path now carried by the plan engine. Pull request #14403
Compose v5.7.0 is out. up now runs Create and Start as one plan over one daemon snapshot for up -d and interactive up; CLI unchanged. Also fixed: duplicate network/volume progress, down --rmi removing images of unselected services, OCI cache consistency, and events --until EOF ha
Compose v5.7.0 is out. For users of Compose as a library, up now runs its Create and Start phases as a single plan over a single daemon snapshot, for up -d and interactive up, as scale, watch rebuilds and start already do. The CLI behaves as before. This week also fixed duplicate network and volume progress in up, create and run; down --rmi local|all removing images of services outside the teardown selection; the extracted OCI project cache staying consistent on interruption and concurrent access; and events --until treating the end of a bounded stream as an error. Smaller changes moved images, logs and attach into their own internal packages without behavior changes and migrated more end-to-end tests to the Scenario DSL.
Week of October 26, 2026
What shipped
- Interactive up now runs on a single plan. Pull request #14305
- An attached up that stops the application itself now honors the -t/--timeout flag instead of waiting for each service's
stop_grace_period. Pull request #14395 - A
depends_oncondition ofservice_healthyorservice_completed_successfullyis now checked before the first 500ms poll tick when the dependency already satisfies it. Pull request #14385 - Down -v no longer removes a named volume the project does not own, such as one labeled for another project or created outside Compose; it skips it with a warning. Pull request #14374
- Compose watch now recognizes a bind-mounted child path whose name begins with two dots, such as..local. Pull request #14425
- The --parallel limit and COMPOSE_PARALLEL_LIMIT are now passed to bake as --jobs, so builds respect the limit again. Pull request #14352
- Compose start now gives a
use_api_socketservice the config file the option promises when its container was created beforehand. Pull request #14393 - Up now rejects incompatible option combinations with a typed api.IncompatibleOptionsError instead of silently ignoring them for library callers. Pull request #14306
- When a service fails to start, up now reports which other services were left unstarted and why. Pull request #14376
- The container monitor now asks the engine for events since before it lists the project's containers, so a container that starts and exits in between is not missed. Pull request #14304
Why it matters
This week's changes fix several things users hit in day-to-day use: the timeout flag on an attached up, slow dependency checks, volumes removed by down -v that the project does not own, and bake builds ignoring the parallel limit. Much of the remaining work moves code out of the flat pkg/compose package into internal packages and prepares the foreground up to run on the plan engine, with new end-to-end tests pinning its behavior.
Changelog entry
- Interactive up runs on a single plan. Pull request #14305
- Attached up honors -t/--timeout when it stops the application itself. Pull request #14395
- A
depends_oncondition is checked before the first poll tick. Pull request #14385 - Down -v keeps named volumes the project does not own and warns instead. Pull request #14374
- Watch recognizes bind-mounted paths starting with two dots. Pull request #14425
- --parallel and COMPOSE_PARALLEL_LIMIT are passed to bake as --jobs. Pull request #14352
- Compose start gives a
use_api_socketservice its config file. Pull request #14393 - Up rejects incompatible option combinations with a typed error. Pull request #14306
- A failed start reports the services it left unstarted. Pull request #14376
- The container monitor subscribes to events since before the initial listing. Pull request #14304
- Unsupported attribute warnings show unescaped service names. Pull request #14380
- Golangci-lint bumped to v2.15.0 and the code fixed to zero findings. Pull request #14418
This week in Compose: attached up now honors -t when it stops the app, depends_on health checks skip the first 500ms wait when already satisfied, down -v keeps volumes the project does not own, --parallel reaches bake as --jobs, and watch handles bind paths starting with two dots
This week in Compose brings several fixes for common workflows. An attached up that stops the application itself now honors the -t/--timeout flag instead of waiting for each service's stop_grace_period. depends_on conditions are checked before the first poll tick, so an already healthy dependency no longer costs an extra wait. down -v now keeps named volumes the project does not own, and warns instead. The --parallel limit and COMPOSE_PARALLEL_LIMIT are passed to bake as --jobs so builds respect the limit again. compose watch recognizes bind-mounted paths starting with two dots, and compose start gives a use_api_socket service its config file. Alongside these, refactoring continues to split pkg/compose into internal packages, and the foreground up gains end-to-end tests ahead of its move t
Week of October 19, 2026
What shipped
- Docker compose watch now ignores changes under the project's.git directory at any depth in the watched path, so git operations are no longer synced into containers and edits no longer trigger endless rebuilds. Pull request #14363
- Docker compose run keeps the anonymous volumes of a recreated dependency when its configuration changed, matching what docker compose up already does, so database dependencies no longer look wiped. Pull request #14358
- A Compose file can now set a service container's umask with the umask attribute, and Compose fails with a clear message on engines that would silently ignore it. Pull request #14367
- Compose updated to go1.26.10, which includes a crypto/x509 security fix that blocks trust in a small set of intermediate certificates. Pull request #14366
- V5.6.1 was released, carrying the go1.26.10 update and the crypto/x509 security fix. Release
- A test-only fix stops TestRunHandlesKeysUntilContextIsDone from being reported as a failure by gotestsum even though it passes. Pull request #14351
Why it matters
This week brings a security update plus two fixes that affect everyday use:.git changes no longer reach containers under watch, and run now preserves a recreated dependency's anonymous volumes. Compose files also gain the umask service attribute for engines that support it.
Changelog entry
- Watch: ignore.git at any depth inside the watched path Pull request #14363
- Run: keep a recreated dependency's anonymous volumes Pull request #14358
- Feat: support the umask service attribute Pull request #14367
- Update to go1.26.10 (security) Pull request #14366
- Release v5.6.1 Release
- Test(formatter): keep escape sequences out of the go test output Pull request #14351
Compose v5.6.1 is out with go1.26.10 and a crypto/x509 security fix. Also this week: watch ignores.git at any depth, run keeps a recreated dependency's anonymous volumes, and the umask service attribute is supported.
Compose v5.6.1 is released, updating to go1.26.10 and including one crypto/x509 security fix that blocks trust in a small set of intermediate certificates. This week also brings two fixes for common workflows. docker compose watch now ignores.git at any depth inside the watched path, so git operations are no longer synced into containers and edits no longer trigger rebuilds that never stop. docker compose run now keeps the anonymous volumes of a recreated dependency whose configuration changed, matching up, so a database dependency no longer looks wiped. Compose files can also set a service container's umask with the umask attribute, with a clear error on engines that would ignore it.
Week of October 12, 2026
What shipped
- Added --ignore-missing to docker compose push so images not present locally are skipped instead of failing the push, with any other error still failing the command. Pull request #14341
- Deprecated push's --ignore-push-failures in favor of --ignore-missing; the old flag still works with a warning, is hidden from help, and cannot be combined with the new one. Pull request #14354
- Added --all-projects and --aggregate flags to docker compose stats; without them the command shows the current project one line per container as before. Pull request #14337
- Docker compose run gained --no-recreate, which reuses existing dependencies as-is instead of recreating them when their config hash differs. Pull request #14144
- A service can now set
use_service_name_aliasto false on a network entry so its name is not registered as a DNS alias on that network. Pull request #14342 - Dry-run for up, create, run, down, stop and pull no longer executes provider services or pulls and configures models. Pull request #14334
- Fixed builds failing with missing entitlement grants since Buildx v0.37.2, caused by Bake enforcing permissions under --progress rawjson. Pull request #14325
- Fixed compose build sometimes losing the reason for a build failure by reading bake's stderr to the end before waiting. Pull request #14335
- Pre_start hooks now run with variables from the
env_fileentries they inherit from the service or declare themselves. Pull request #14293 - Fixed watch so sync+exec triggers on bind-mounted paths are skipped with a warning instead of being monitored. Pull request #14328
Why it matters
This week brings two new opt-in flags to stats and a safer push option for images missing locally, plus a way for run to keep existing dependency state. Several fixes target builds and hooks: dry-run no longer executes providers or models, builds keep their failure reason and permissions, and pre_start hooks get their env_file variables.
Changelog entry
- Push: add --ignore-missing to skip images not available locally Pull request #14341
- Push: deprecate --ignore-push-failures in favor of --ignore-missing Pull request #14354
- Stats: add --all-projects and --aggregate flags Pull request #14337
- Run: add --no-recreate to reuse existing dependencies as-is Pull request #14144
- Network: let a service opt out of its name as a network alias Pull request #14342
- Dry-run: do not execute providers and models Pull request #14334
- Build: grant permissions for configured build inputs Pull request #14325
- Build: read bake's stderr to the end before waiting Pull request #14335
- Pre_start: hooks receive the service
env_fileand environment Pull request #14293 - Watch: skip sync+exec triggers on bind-mounted paths Pull request #14328
This week in docker/compose: push got --ignore-missing and --ignore-push-failures is deprecated, stats added --all-projects and --aggregate, and run gained --no-recreate. Also fixes for build errors being dropped, bake permissions, dry-run executing providers, and pre_start hook
This week in docker/compose: push has a new --ignore-missing flag that skips images not available locally, and --ignore-push-failures is now deprecated in its favor. docker compose stats added opt-in --all-projects and --aggregate flags. docker compose run gained --no-recreate to reuse existing dependencies as-is. On the fix side: build now reads bake's stderr to the end so failure reasons are not dropped, missing entitlement grants with recent Buildx are handled, dry-run no longer executes providers or models, pre_start hooks receive their env_file variables, and watch skips sync+exec triggers on bind-mounted paths. Services can also opt out of their name as a network alias with use_service_name_alias.
Week of October 5, 2026
What shipped
- Compose reads Docker Hub credentials from the account signed in to Docker Desktop before falling back to the Docker CLI config file and its credential helpers. Pull request #14295
- Fixed a bug where a container that restarts while Compose is following its logs no longer prints the same log line twice. Pull request #14314
- The plan executor now runs start-phase operations such as waiting on a dependency's condition and running pre-start steps. Pull request #14274
- DownOptions.Images is now a typed ImagePruneMode validated upfront instead of a bare string validated only after containers were already removed. Pull request #14149
- An optional dependency whose health check wait is cancelled or times out is no longer reported as skipped. Pull request #14309
- Bridge commands now reject the --dry-run flag instead of silently ignoring it and performing real changes. Pull request #14307
- Removed a broken CONTRIBUTING.md link from the documentation. Pull request #14251
Why it matters
This week brings fixes and groundwork that affect everyday use: credentials for Docker Hub images now come from the Docker Desktop sign-in, restarting containers no longer duplicate log lines, and mistyped image prune modes fail before teardown begins. Progress on the plan executor also moves Compose toward running start-phase operations directly. Overall the week reduces surprising behavior and halves-finished operations for people using Compose.
Changelog entry
- Compose reads Docker Hub credentials from the Docker Desktop sign-in before falling back to the Docker CLI config file and its credential helpers. Pull request #14295
- Fixed duplicate log lines when a container restarts while logs are being followed. Pull request #14314
- DownOptions.Images is now a typed ImagePruneMode validated upfront. Pull request #14149
- A cancelled or expired wait on an optional dependency is no longer reported as skipped. Pull request #14309
- Bridge commands now reject --dry-run instead of silently ignoring it. Pull request #14307
- The plan executor now runs start-phase operations. Pull request #14274
- Removed a broken CONTRIBUTING.md link. Pull request #14251
This week in Compose: Docker Hub credentials now come from the signed-in Docker Desktop account, restarting containers no longer double-print log lines, DownOptions.Images is a validated type, optional dependency waits that are cancelled are no longer called skipped, and the plan
This week in Compose, several changes improve correctness for everyday use. Compose now reads Docker Hub credentials from the account signed in to Docker Desktop, before falling back to the Docker CLI config file and its credential helpers. A container that restarts while Compose follows its logs no longer prints the same line twice. DownOptions.Images is now a typed ImagePruneMode validated upfront, so a bad value fails before down removes containers rather than after. Optional dependencies whose health check wait is cancelled or hits its deadline are no longer reported as skipped. Bridge commands reject --dry-run instead of ignoring it. The plan executor now runs start-phase operations, and a broken CONTRIBUTING.md link was removed.
Week of September 28, 2026
What shipped
- V5.6.0 released with partial support for manually-triggered jobs; scheduled jobs will be added once Docker Engine support is available. Release
- Provider-backed services now participate in the image phase, allowing build and image declarations on provider services to reach the provider's runtime. Pull request #14252
- Provider relay links now get their own dedicated bridge network instead of relying on providers to guess bind addresses. Pull request #14275
- Fixed --dry-run hanging when services depend on others via
depends_onwithservice_completed_successfullycondition. Pull request #14270 - Pre_start hook containers are now first-class resources in the reconciliation plan, created by the plan rather than during the start phase. Pull request #14221
- Docker compose down --rmi no longer prints misleading dangling image removal messages when there's nothing to clean up. Pull request #14266
- Fixed compatibility with compose-go v2.16.1 which silently promotes the deprecated x-initialSync extension to
initial_sync. Pull request #14281 - Fixed --parallel flag not being honored across all bulk engine calls due to incorrect concurrency limit handling. Pull request #14177
- Removed duplicate publish command registration under alpha after it was promoted to a regular Compose command. Pull request #14272
Why it matters
This release brings improved job support with provider integration, fixes critical bugs in dry-run and service dependencies, and strengthens the provider experience with dedicated networking. Several correctness issues around parallelism and cleanup output are also resolved.
Changelog entry
- Add partial support for manually-triggered jobs (scheduled jobs coming when Docker Engine support lands) Release
- Provider services now participate in image phase with on-demand image distribution Pull request #14252
- Provider relay links get dedicated bridge networks per service Pull request #14275
- Fix --dry-run hanging with
depends_on: condition:service_completed_successfullyPull request #14270 - Pre_start hook containers are now reconciliation plan resources Pull request #14221
- Fix docker compose down --rmi printing misleading dangling image messages Pull request #14266
- Fix --parallel flag not being honored across bulk engine calls Pull request #14177
- Adapt to compose-go v2.16.1 silent x-initialSync promotion Pull request #14281
- Remove duplicate publish command registration under alpha Pull request #14272
Docker Compose v5.6.0 is out. Partial job support for manually-triggered jobs, improved provider integration with image distribution, dedicated networks for provider relays, and fixes for --dry-run and --parallel.
Docker Compose v5.6.0 is available. This release adds partial support for manually-triggered jobs, improves provider-backed services with dedicated bridge networks and image phase participation, and fixes several issues including --dry-run hangs with service dependencies and --parallel flag handling across bulk operations.
Week of September 21, 2026
What shipped
- Provider migration now works correctly — migrating a deployed service to a provider replaces old containers instead of failing on name conflicts. Pull request #14264
- Providers can now query where to bind their relay endpoint so it reaches them on every platform without exposing ports on the LAN. Pull request #14258
- The plan engine now describes the start phase of applications, extending its vocabulary beyond just creation. Pull request #14200
- Service config-hash byte layout is pinned to prevent compose-go struct refactorings from invalidating existing container stamps. Pull request #14215
- Fixed races in restart re-attach anchoring, shutdown log draining, and wait behavior that were causing flaky tests. Pull request #14140
- Fixed --project-directory being ignored when working with OCI artifacts, now correctly resolving relative volume paths. Pull request #14234
- Services reachable only through another service's build.additional_contexts now build correctly even when their own profile is inactive. Pull request #14242
- Fixed e2e test assertions for pull failures to handle daemon-backend dependent error messages and stderr output. Pull request #14245
Why it matters
Provider migration support and relay binding enable better multi-platform deployments. The plan engine improvements and hash pinning strengthen internal architecture while fixes to restart behavior and profile handling address real user issues.
Changelog entry
- Fix provider migration to replace stale service replicas instead of failing on container name conflicts Pull request #14264
- Add get-relay-info command so providers can query where to bind published endpoints Pull request #14258
- Extend plan engine to describe the start phase of applications Pull request #14200
- Pin service config-hash byte layout to prevent compose-go struct refactorings from invalidating container stamps Pull request #14215
- Fix restart re-attach anchor, shutdown log draining, and wait behavior races Pull request #14140
- Fix --project-directory being ignored when using OCI artifacts Pull request #14234
- Fix services in build.additional_contexts to build when referenced service profile is inactive Pull request #14242
- Adopt compose-go jobs and container-spec layering with
pre_starthooks Pull request #14093
This week: provider migration works, relays bind intelligently, plan engine handles start phases, and config hashes stay stable across refactors. Plus fixes for restart races and profile handling.
This week in docker/compose: provider migration now works seamlessly without name conflicts. Providers can query relay binding locations for cross-platform compatibility. The plan engine extends to describe application start phases. Config-hash layout is pinned to prevent future invalidation. Multiple fixes address restart re-attach races, OCI project directories, and service profile handling.