Review Privileges and Install a Plugin

Review Privileges and Install a Plugin

Inspect a plugin's requested privileges, install it, enable it, and verify.

1. Read what the plugin is asking for before installing anything. The response enumerates each privilege — network mode, mount points, devices, capabilities — and is the natural place to gate on policy or human review.
2. Pull and install the plugin, echoing the reviewed privilege set back in the body as an explicit acknowledgement of what is being granted. The plugin is installed but inert after this call.
3. Enable the installed plugin. Installation alone does not activate a plugin — until this call it is present but does nothing.
4. Inspect the plugin to confirm the daemon reports it enabled, and capture the settings it was actually granted so they can be reconciled against what was requested in the first step.

What you'll need to have ready

• remote: Remote reference for the plugin to install (e.g. "vieux/sshfs:latest").
• localName: Local name to give the installed plugin.
• privileges: The privilege set to acknowledge on install. This should be the value read back from the privileges step, reviewed by a human or a policy check before being ech
• enableTimeout: HTTP client timeout in seconds for the enable call.
• registryAuth: Base64url-encoded auth configuration for pulling from a private registry.

For your developer

Arazzo workflow docker:install-plugin, 4 operations: GetPluginPrivileges → PluginPull → PluginEnable → PluginInspect. Specs on APIs.io.