1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55
/*
* supports a RESTful API for the Libpod library
*
* This documentation describes the Podman v2.x+ RESTful API. It consists of a Docker-compatible API and a Libpod API providing support for Podman’s unique features such as pods. To start the service and keep it running for 5,000 seconds (-t 0 runs forever): podman system service -t 5000 & You can then use cURL on the socket using requests documented below. NOTE: if you install the package podman-docker, it will create a symbolic link for /run/docker.sock to /run/podman/podman.sock NOTE: Some fields in the API response JSON are encoded as omitempty, which means that if said field has a zero value, they will not be encoded in the API response. This is a feature to help reduce the size of the JSON responses returned via the API. NOTE: Due to the limitations of [go-swagger](https://github.com/go-swagger/go-swagger), some field values that have a complex type show up as null in the docs as well as in the API responses. This is because the zero value for the field type is null. The field description in the docs will state what type the field is expected to be for such cases. See podman-system-service(1) for more information. Quick Examples: 'podman info' curl --unix-socket /run/podman/podman.sock http://d/v5.0.0/libpod/info 'podman pull quay.io/containers/podman' curl -XPOST --unix-socket /run/podman/podman.sock -v 'http://d/v5.0.0/images/create?fromImage=quay.io%2Fcontainers%2Fpodman' 'podman list images' curl --unix-socket /run/podman/podman.sock -v 'http://d/v5.0.0/libpod/images/json' | jq
*
* The version of the OpenAPI document: 5.0.0
* Contact: podman@lists.podman.io
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
/// MountPoint : This is used for reporting the mountpoints in use by a container.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct MountPoint {
/// Destination is the path relative to the container root (`/`) where the Source is mounted inside the container.
#[serde(rename = "Destination", skip_serializing_if = "Option::is_none")]
pub destination: Option<String>,
/// Driver is the volume driver used to create the volume (if it is a volume).
#[serde(rename = "Driver", skip_serializing_if = "Option::is_none")]
pub driver: Option<String>,
/// Mode is a comma separated list of options supplied by the user when creating the bind/volume mount. The default is platform-specific (`\"z\"` on Linux, empty on Windows).
#[serde(rename = "Mode", skip_serializing_if = "Option::is_none")]
pub mode: Option<String>,
/// Name is the name reference to the underlying data defined by `Source` e.g., the volume name.
#[serde(rename = "Name", skip_serializing_if = "Option::is_none")]
pub name: Option<String>,
#[serde(rename = "Propagation", skip_serializing_if = "Option::is_none")]
pub propagation: Option<String>,
/// RW indicates whether the mount is mounted writable (read-write).
#[serde(rename = "RW", skip_serializing_if = "Option::is_none")]
pub rw: Option<bool>,
/// Source is the source location of the mount. For volumes, this contains the storage location of the volume (within `/var/lib/docker/volumes/`). For bind-mounts, and `npipe`, this contains the source (host) part of the bind-mount. For `tmpfs` mount points, this field is empty.
#[serde(rename = "Source", skip_serializing_if = "Option::is_none")]
pub source: Option<String>,
#[serde(rename = "Type", skip_serializing_if = "Option::is_none")]
pub r#type: Option<String>,
}
impl MountPoint {
/// This is used for reporting the mountpoints in use by a container.
pub fn new() -> MountPoint {
MountPoint {
destination: None,
driver: None,
mode: None,
name: None,
propagation: None,
rw: None,
source: None,
r#type: None,
}
}
}