Skip to content

Conversation

@thaJeztah
Copy link
Member

This documents the Service privileges API changes, that were added in: moby/moby@091b5e6 (moby/moby#32339)

Carries the CLI changes of moby/moby#32483, with some additional information about the values

ping @johnstep PTAL

@thaJeztah
Copy link
Member Author

Also ping @albers PTAL

@codecov-io
Copy link

codecov-io commented Jul 15, 2017

Codecov Report

Merging #338 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #338      +/-   ##
==========================================
+ Coverage   48.83%   48.85%   +0.01%     
==========================================
  Files         186      186              
  Lines       12413    12413              
==========================================
+ Hits         6062     6064       +2     
+ Misses       5977     5975       -2     
  Partials      374      374

For example, specifying `file://spec.json` loads
`C:\ProgramData\Docker\CredentialSpecs\spec.json`.

When using the `registry://keyname` format, the credential spec is read
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove keyname here since this only needs to state the prefix (and, technically, it is a value not a key).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Darn, copied the wrong one; I can make it registry://<value name>

When using the `registry://keyname` format, the credential spec is read
from the Windows registry on the daemon's host. The specified registry
value must be located in `HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Virtualization\Containers\CredentialSpecs`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be a space between Windows and NT. Is that going to be clear?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, I see it wrapped; hold on, fixing

@thaJeztah
Copy link
Member Author

Updated, PTAL

Copy link
Contributor

@johnstep johnstep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah thaJeztah added this to the 17.06.1 milestone Jul 15, 2017
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah
Copy link
Member Author

author LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants