Eric Hripko

This definitely sounds like a usability gap, so it makes sense to me that this feature is added and surfaced in the volume declaration 👍

Sounds like your use case may be satisfied by `condition: service_healthy`, which I'm trying to bring in from v2 Compose in https://github.com/compose-spec/compose-spec/issues/68 and https://github.com/compose-spec/compose-spec/pull/72.

Maybe it'd make sense to follow the [k8s probe model](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)? HTTP/TCP checks should cover quite a lot of cases in theory. The caveat here is very fairly pointed out by...

I believe _Implementations_ section refers to tools that work with Compose file format. Unfortunately, I don't think the spec explicitly lists the compatibility of CLI with various attributes. I'm hoping...

Hi @marcusx - thank you for sharing your question 👍 Could you check if `docker-compose config` correct prints out your configuration?

I wonder - what's the advantage of taking this approach over using service-mode versions of `network_mode`/`pid`/`ipc` attributes to share namespaces?

Hey folks! Is there any workaround we could use in the meantime? We're facing issues where some features/bugfixes in _Remote - Containers_ require the latest version whilst this requires an...

Hi folks! I've made a barebones BuildKit frontend (available [here](https://github.com/EricHripko/cnbp)). It's doesn't offer the full functionality/spec compatibility, but would love to hear your feedback 🙂

Right now the frontend isn't doing anything smart when it comes to reusing launch layers (thus every build is from scratch). That being said, I think `MergeOp` isn't (strictly speaking)...

> From [buildpacks/lifecycle#423 (comment)](https://github.com/buildpacks/lifecycle/issues/423#issuecomment-811974384): I was going to comment along the same lines. Being quite new to BuildPacks, I found it surprising (in terms of separation of concerns) that _lifecycle_...