a9edb0d230
The mount type is used across common GRPC services to express a deferred access of a filesystem. Right now, they are generated by snapshotters, but eventually, they can be passed for containers for creation at runtime. With this flow, we can separate the generation and use of a root container filesystem. Signed-off-by: Stephen J Day <stephen.day@docker.com>
27 lines
823 B
Protocol Buffer
27 lines
823 B
Protocol Buffer
syntax = "proto3";
|
|
|
|
package containerd.v1.types;
|
|
|
|
import "github.com/gogo/protobuf/gogoproto/gogo.proto";
|
|
|
|
// Mount describes mounts for a container.
|
|
//
|
|
// This type is the lingua franca of ContainerD. All services provide mounts
|
|
// to be used with the container at creation time.
|
|
//
|
|
// The Mount type follows the structure of the mount syscall, including a type,
|
|
// source, target and options.
|
|
message Mount {
|
|
// Type defines the nature of the mount.
|
|
string type = 1;
|
|
|
|
// Source specifies the name of the mount. Depending on mount type, this
|
|
// may be a volume name or a host path, or even ignored.
|
|
string source = 2;
|
|
|
|
// Target path in container
|
|
string target = 3;
|
|
|
|
// Options specifies zero or more fstab style mount options.
|
|
repeated string options = 4;
|
|
}
|