Docker-Compose: order of cap_drop and cap_add?

The docker compose file reference describes the cap_add and cap_drop elements in a rather terse fashion:

Add or drop container capabilities. See man 7 capabilities for a full list.

Do these elements have an order, that is, add first, then drop? Or does the order matter (is this supported in YAML at all for dictionaries?)?

What happens when one of cap_add or cap_drop contains ALL?

I'm aware of the Docker Linux default set of capabilities, defined in https://github.com/moby/moby/blob/master/oci/caps/defaults.go#L4.

After diving around the moby source code, I finally located TweakCapabilities(): it takes the two sets of capabilities to add and to drop, enforcing the following scheme below; thus works in docker-compose.yaml where YAML doesn't define an order for the cap_add and cap_drop keys. The first matching item below will terminate the list.

• container is privileged: true: ignore cap_add and cap_drop completely, return all available capabilities instead.
• both cap_add and cap_drop are empty: return the default Docker set of capabilities.
• cap_add contains ALL: return all capabilities minus the capabilities listed in cap_drop (ignores ALL in the latter).
• cap_drop contains ALL: return the capabilities from cap_add only, ignoring any Docker default capabilities.
• default: first drop all capabilites from the default set listed in cap_drop, then add the capabilities in cap_add, and finally return the result.

If I'm not mistaken this can be also represented in a more accessible manner as follows...

In the end, there's only the following two "deterministic" combinations that always include cap_drop: ALL and that follow the line of least privilege: