38de272bd4
When the daemon is configured to run with an authorization-plugin and if the plugin is disabled, the daemon continues to send API requests to the plugin and expect it to respond. But the plugin has been disabled. As a result, all API requests are blocked. Fix this behavior by removing the disabled plugin from the authz middleware chain. Tested using riyaz/authz-no-volume-plugin and observed that after disabling the plugin, API request/response is functional. Fixes #31836 Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com>
26 lines
635 B
Go
26 lines
635 B
Go
package plugin
|
|
|
|
import (
|
|
"sync"
|
|
|
|
"github.com/docker/docker/pkg/plugins"
|
|
"github.com/docker/docker/plugin/v2"
|
|
)
|
|
|
|
// Store manages the plugin inventory in memory and on-disk
|
|
type Store struct {
|
|
sync.RWMutex
|
|
plugins map[string]*v2.Plugin
|
|
/* handlers are necessary for transition path of legacy plugins
|
|
* to the new model. Legacy plugins use Handle() for registering an
|
|
* activation callback.*/
|
|
handlers map[string][]func(string, *plugins.Client)
|
|
}
|
|
|
|
// NewStore creates a Store.
|
|
func NewStore() *Store {
|
|
return &Store{
|
|
plugins: make(map[string]*v2.Plugin),
|
|
handlers: make(map[string][]func(string, *plugins.Client)),
|
|
}
|
|
}
|