nicolas de loof

@bsideup I always have missed some "how to" metadata aside docker images, which would offer guidance on required env variables, recommended memory etc... Publishers use to offer a README but a machine-readable form would have been nice

This essentially allows publishing compose.yaml next to the original image (maybe as a baked-in metadata in the same OCI artifact?) that provides "patterns of usage" with Docker Compose being the definition language

Okay, looks like all the use cases I thought of are semi-blocked by github.com/docker/compose… Interesting that it is a publish-stage measure and not runtime, and a custom-compiled docker-compose allows you to publish a Compose file that can mount folders 👀 cc @glours

@VolcampIO @glours mais qu'on est bô !

#Conference "Compose to Kube, same player shoot again" par @glours et Nicolas De Loof à @VolcampIO