Volumes¶
MKE uses named volumes to persist data on all nodes on which it runs.
Volume name |
Contents |
---|---|
|
Certificate and keys for the authentication and authorization service. |
|
Certificate and keys for the authentication and authorization store. |
|
Data of the authentication and authorization store, replicated across managers. |
|
Certificate and keys for authentication worker. |
|
Data of the authentication worker. |
|
Root key material for the MKE root CA that issues client certificates. |
|
Root key material for the MKE root CA that issues certificates for swarm members. |
|
Certificate and keys that the MKE web server uses to communicate with other MKE components. |
|
Certificate and keys for the MKE web server running in the node. |
|
MKE configuration data, replicated across managers. |
|
Certificates and keys for the key-value store. |
|
Monitoring data that MKE gathers. |
|
Configuration file that the |
|
Certificate and keys for node communication. |
|
Backup artifacts that are created while processing a backup. The artifacts persist on the volume for the duration of the backup and are cleaned up when the backup completes, though the volume itself remains. |
|
Symlinks to MKE component log files, created by |
|
Audit logs streamed by |
Volume name |
Contents |
---|---|
|
Certificate and keys for node communication. |
|
Symlinks to MKE component log files, created by |
You can customize the volume driver for the volumes by creating the volumes prior to installing MKE. During installation, MKE determines which volumes do not yet exist on the node and creates those volumes using the default volume driver.
By default, MKE stores the data for these volumes at
/var/lib/docker/volumes/<volume-name>/_data
.