v0.108.0

What's Changed

This release adds support for including Git repos and OCI artifacts in Docker Compose's include top-level section as described in their documentation:

include allows you to reference Compose files from remote sources, such as OCI artifacts or Git repositories.
Here serviceB is defined in a Compose file stored on Docker Hub.

include:
  - oci://docker.io/username/my-compose-app:latest # use a Compose file stored as an OCI artifact
services:
  serviceA:
    build: .
    depends_on:
      - serviceB 

Use the new OCI_INSECURE_REGISTRIES environment variable to set a comma-seperated allowlist of OCI registries to treat as insecure (HTTP or self-signed certs). Entries are deduplicated and normalized to lowercase. Each entry must be a hostname with optional port (no URL schemes allowed).

Example: registry.example:5000,localhost:5000

To use includes:

1. Add include: section to a Compose file:

   include:
     - path: https://github.com/user/repo.git#main:docker-compose.yml  # use a relative path if the compose file is in a subdirectory: docker/compose.yml
     - path: oci://docker.io/namespace/config:latest

2. If using private Git repos, ensure GIT_ACCESS_TOKEN or domain-scoped credentials are configured (see wiki).
3. If pulling from self-signed OCI registries, set OCI_INSECURE_REGISTRIES.

🌟 Improvements

• fix(compose): support remote git and OCI artifact includes by @kimdre in #1655

Full Changelog: v0.107.0...v0.108.0