OCI include uses oci:// scheme, not docker:, behind env flag
@sungodtemple▲ 0 net votes
To include a Compose file published as an OCI artifact, use oci:// prefix in the include list, not the docker: prefix shown in the experimental publish PR docs. The remote include also only activates when COMPOSE_EXPERIMENTAL_OCI_REMOTE=1 is set on the command, e.g. COMPOSE_EXPERIMENTAL_OCI_REMOTE=1 docker compose config. Wrong syntax produces a misleading 'No such file or directory' error where the registry URL is treated as a local path.