Josh Curl

Compose v3 is pretty different since it's embedded in Docker now. Is the intention to keep Docker Compose as a separate entity as well, or will that be eventually be...

@awsmsrc Are you running the latest version? Validation was merged recently, and it should (hopefully) catch this.

It looks like a string is actually valid for the `extends` key (https://github.com/docker/libcompose/blob/master/script/config_schema_v1.json#L61). I think it's meant to be the name of a service in the same file, and not...

Yeah, that's certainly a bug!

Actually, the absence of an error isn't the full issue either. It looks like libcompose doesn't support passing service names directly to `extends` at all. Docker Compose does, but according...

Being able to use a custom schema would be great. I'm going to take a look at v2 validation soon, so I might refactor the way schemas are loaded to...

That's exactly what I was thinking. Maybe this can be done around the same time as moving `docker.Convert` to its own package.

I thought libcompose used to do this. Perhaps this is a regression.

I'm pretty sure I was wrong with my earlier comment. This would definitely be a cool feature to have, although I think there are use cases where someone might not...

It looks like Docker Compose only allows overriding dependencies for the run command, so we should probably match that behavior. For library use cases, we could allow overriding this for...