We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Most of 3rd party services that define a resource reservation do it by setting a label such as:
{"Resources" {"Reservations":{"NanoCPUs":123}}}
This is wrong and should be:
{"Resources" {"Reservation":{"NanoCPUs":123}}}
see https://docs.docker.com/engine/api/v1.41/#operation/ServiceCreate
Nevertheless we should also keep backward compatibility.
For info @pcrespov , @GitHK , @mguidon , @odeimaiz
The text was updated successfully, but these errors were encountered:
actually this was a wrong assessment, and the Docker REST API has been corrected. It's "Reservations"
Sorry, something went wrong.
sanderegg
No branches or pull requests
Most of 3rd party services that define a resource reservation do it by setting a label such as:
This is wrong and should be:
see https://docs.docker.com/engine/api/v1.41/#operation/ServiceCreate
Nevertheless we should also keep backward compatibility.
For info @pcrespov , @GitHK , @mguidon , @odeimaiz
The text was updated successfully, but these errors were encountered: