Nicolas De loof
Nicolas De loof
the issue is in compose-go, which "extends" `6005-6015:5000` into a list of bindings for each and every values in the range
compose-go both extends port range to a list of ports, but also [assumes this is expected](https://github.com/compose-spec/compose-go/blob/master/types/types_test.go#L116-L135) and types are [designed](https://github.com/compose-spec/compose-go/blob/master/types/types.go#L581-L582) to only accept an actual port (`uint32`) not range. I...
This will also require some clarification on https://github.com/compose-spec/compose-spec/blob/master/spec.md#ports if we want this to be addressed + the compose spec schema does not allow use of a string as `published` port...
Compose v1 development is now paused as Compose v2 has been release. I don't expect some significant progress made for this issue regarding the python codebase.
@thaJeztah maybe you know some magic hook we could use here to only get the relevant "after container restarted" logs from history?
right, maybe timeNano, can't remember. When I tried using this is didn't helped
Since: Only return logs since this time, as a UNIX timestamp
need TestComposePull to be fixed
@crazy-max any thoughts?
@thaJeztah buildkit indeed consider the build requests we schedule in parallel for services to be fully independent, and as such won't do any magic on concurrent pulls for same layers....