Morio Core API (0.5.5)

This will cause an ephemeral node to join a cluster

This is the cluster heartbeat endpoint, which is where follower nodes will contact the leader node in a Morio cluster

Generates an X.509 certificate, issued by Morio's internal Certificate Authority

Decrypts data with Morio's internal key pair

Encrypts data with Morio's internal key pair

This is a proxy endpoint for the Docker API on the host system that returns list of all containers available on the host system.

To only get the running containers, use the /docker/containers endpoint instead.

This is a proxy endpoint for the Docker API on the host system that returns the list of containers currently running on the hoste sytem.

To get all containers, use the /docker/allcontainers endpoint instead.

This is a proxy endpoint for the Docker API on the host system that returns information on the used and available storage on the host sytem.

This endpoint is named after the the df command on Linux.

This is a proxy endpoint for the Docker API on the host system that returns the list of Docker images available on the host system.

This is a proxy endpoint for the Docker API on the host system that returns general information about the Docker daemon on the host system.

This is a proxy endpoint for the Docker API on the host system that returns a list of Docker networks on the host system.

This is a proxy endpoint for the Docker API on the host system that returns information on the version of Docker that is running on the host system.

This is a proxy endpoint for the Docker API on the host system that returns information on the container with the ID passed as a parameter in the URL.

This endpoint is equivalent to running the inspect command on a container in the Docker CLI.

Note that Docker accepts an ID or (unambigious) name as input.

This is a proxy endpoint for the Docker API on the host system that returns logs from the container with the ID passed as a parameter in the URL.

This endpoint is equivalent to running the logs command on a container in the Docker CLI.

Note that Docker accepts an ID or (unambigious) name as input.

This is a proxy endpoint for the Docker API on the host system that returns stats based on resource usage from the container with the ID passed as a parameter in the URL.

These stats come from a container'se inspect command in the Docker CLI.

Note that Docker accepts an ID or (unambigious) name as input.

This is a proxy endpoint for the Docker API on the host system that returns information on the image with the ID passed as a parameter in the URL.

This endpoint is equivalent to running the inspect command on an image in the Docker CLI.

Note that Docker accepts an ID or (unambigious) name as input.

This is a proxy endpoint for the Docker API on the host system that returns information on the network with the ID passed as a parameter in the URL.

This endpoint is equivalent to running the inspect command on a network in the Docker CLI.

Note that Docker accepts an ID or (unambigious) name as input.

This changes, or attempts to change, the container state by issuing a kill command.

This changes, or attempts to change, the container state by issuing a pause command.

This changes, or attempts to change, the container state by issuing a restart command.

This changes, or attempts to change, the container state by issuing a start command.

This changes, or attempts to change, the container state by issuing a stop command.

This changes, or attempts to change, the container state by issuing a unpause command.

This will trigger the build of a .deb client package.

Note that this will start an ephemeral container to start the build. This API endpoint will not wait for the build to complete before retuning.

This will return the default values to create a new .deb client package.

Note that configuration of a .debpackage needs to be correct or the package will not function. You can adapt these defaults (that's why we provide them), but should consult the Debian documnentation on packaging.

Returns the current Morio settings.

Note that Morio will encrypt all secrets and remove them from the settings. So this endpoint returns data that is safe to backup.

This will take a full set of new Morio settings and, after validation, apply them.

Note that this endpoint requires you to post the full settings, so when making updates, make sure to leave nothing behind.

This will set up Morio with the provided initial settings.

This endpoint is only available in ephemeral Mode. In other words, once Morio is set up, this endpoint becomes unavailable.

Returns information about the current status of Morio core.

This will return all the data required to bootstrap the Morio Management API, including the settings, presets, and keys.