Nicolas De loof

Compose file format is now managed by the compose-spec.io This one supports all of the V2 and V3 legacy formats, as a "version-less" compose file. But `docker stack` does not...

right, I've been confused by the naming used on `ContainerContext`. Would have used `ContainerDecorator` or something like this, `Context` doesn't make any sense to me here.

For legacy reason those terms have been (mis)used in many ways. Nomenclature is clarified by https://github.com/opencontainers/distribution-spec/blob/main/spec.md#definitions For backward compatibility, `docker tag` command still used a non-strict vocabulary, i.e. one pass...

> there are many parts of the documentation that refer to 'untagged imaged' or 'removing a tag from an image' when they are actually talking about full identifiers, not just...

doens't work out of the box, can't load `/engine/api/v1.41.yaml` on netlify preview also breaks CSS customization we made for docs.docker.com

Agree. `--filter` is one of the worst part of the docker UX. Better documentation (at least) and better consistency would be a nice enhancement

I don't think "Copied from github.com/docker/docker/registry.ConvertToHostname to reduce dependencies" makes our codebase better. 1. we still (obviously) depend on docker/docker as the API is not an isolated project vs engine...

I didn't noticed the v3.0.0 release, this is something we should consider for next release, wdyt @glours @ulyssessouza ?

we indeed don't support yaml.v3 (yet), see https://github.com/compose-spec/compose-go/pull/153

`extension` is indeed used internally to collect all `x-..` attributes. This is unfortunate. I'll look into a fix