You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the problem you're trying to solve
A clear and concise description of what the problem is.
In the Compose deploy specification, the placement attribute does not match the JSON schema. Docker compose (v2.24.6) seems to conform to the schema and not the specification.
Describe the solution you'd like
A clear and concise description of what you'd like to happen.
The specification, schema, and reference implementation (docker compose) should agree on what is acceptable for the deploy placement attribute. I don't have a particular interest in what they agree on, just that they agree.
Additional context
Add any other context about the feature request here.
None.
The text was updated successfully, but these errors were encountered:
k9withabone
changed the title
Deploy placement constraint specification doesn't match schema
Deploy placement specification doesn't match schema
Feb 28, 2024
Looking at the deploy specification more closely, it seems that it could use a review in general to make sure the schema and specification match. For example, the resources attribute in the specification is lacking a description of the generic_resources listed in the schema.
What is the problem you're trying to solve
A clear and concise description of what the problem is.
In the Compose deploy specification, the placement attribute does not match the JSON schema. Docker compose (v2.24.6) seems to conform to the schema and not the specification.
Describe the solution you'd like
A clear and concise description of what you'd like to happen.
The specification, schema, and reference implementation (docker compose) should agree on what is acceptable for the deploy placement attribute. I don't have a particular interest in what they agree on, just that they agree.
Additional context
Add any other context about the feature request here.
None.
The text was updated successfully, but these errors were encountered: