Abstract: A diagnostics collection script is included in a container image. When an original instance of the container fails, a new instance of the container is started using the container image using a Docker compose YAML file having the diagnostics collection script as an entrypoint. The diagnostics collection script is configured to collect the logs of the original (now failed) container during the container start operation. In this manner, the container is able to be started in a safe mode and is isolated to only run the diagnostics collection script without disturbing the container's original settings. By recreating the exact environment of the failed container, and running diagnostics on the environment, it is possible to obtain the log files from the original container as well as to implement diagnostic operations on the environment of the original container, which can then be used to help diagnose why the original container failed.

Abstract: An example methodology includes, by a container hosted on a computing device, receiving a request to access the container, the request including a temporary username and password and an access group to which a user associated with the request belongs. The method also includes, by the container, creating a temporary user credentials based on the temporary username and password, adding the user to the container, mapping the access group passed with the request to an equivalent predefined access group within the container, and assigning the user to the equivalent predefined access group, wherein the predefined access group within the container specifies permissions to be granted to the user. The method further includes, by the container, providing access to the container based on the temporary user credentials and the equivalent predefined access group and sending a response to the request, the response including information about the provided access to the container.

Abstract: According to one aspect of the disclosure, a method includes: determining a plurality of network addresses assigned to an application, the application being deployed within a container on a host; determining a plurality of network addresses assigned to the container; and configuring networking of the host and of the container to establish routes between at least a first one of the plurality of network addresses assigned to the application and at least a first one of the plurality of network addresses assigned to the container.

Abstract: An example methodology includes, by a container hosted on a computing device, receiving a request to access the container, the request including a temporary username and password and an access group to which a user associated with the request belongs. The method also includes, by the container, creating a temporary user credentials based on the temporary username and password, adding the user to the container, mapping the access group passed with the request to an equivalent predefined access group within the container, and assigning the user to the equivalent predefined access group, wherein the predefined access group within the container specifies permissions to be granted to the user. The method further includes, by the container, providing access to the container based on the temporary user credentials and the equivalent predefined access group and sending a response to the request, the response including information about the provided access to the container.

Abstract: According to one aspect of the disclosure, a method includes: determining a plurality of network addresses assigned to an application, the application being deployed within a container on a host; determining a plurality of network addresses assigned to the container; and configuring networking of the host and of the container to establish routes between at least a first one of the plurality of network addresses assigned to the application and at least a first one of the plurality of network addresses assigned to the container.

Abstract: Failover of a Docker container between nodes of a cluster is orchestrated to enable the Docker container's data to be made available across all nodes of the cluster. Using this orchestration system, if a second cluster node is selected to be used to bring up a Docker container, the orchestration system coordinates destroying the previous Docker volumes on the first cluster node, unmounting a physical device containing the application data from the first cluster node's virtual filesystem, remounting the physical device containing the application data in the virtual filesystem of the second cluster node, creating a Docker volume referencing the application data on the second cluster node, and using the Docker volume to start a new instance of the Docker container on the second cluster node. This enables the Docker container to be started on any node of a cluster and have the application data available as a local filesystem.

Abstract: Failover of a Docker container between nodes of a cluster is orchestrated to enable the Docker container's data to be made available across all nodes of the cluster. Using this orchestration system, if a second cluster node is selected to be used to bring up a Docker container, the orchestration system coordinates destroying the previous Docker volumes on the first cluster node, unmounting a physical device containing the application data from the first cluster node's virtual filesystem, remounting the physical device containing the application data in the virtual filesystem of the second cluster node, creating a Docker volume referencing the application data on the second cluster node, and using the Docker volume to start a new instance of the Docker container on the second cluster node. This enables the Docker container to be started on any node of a cluster and have the application data available as a local filesystem.

Abstract: A diagnostics collection script is included in a container image. When an original instance of the container fails, a new instance of the container is started using the container image using a Docker compose YAML file having the diagnostics collection script as an entrypoint. The diagnostics collection script is configured to collect the logs of the original (now failed) container during the container start operation. In this manner, the container is able to be started in a safe mode and is isolated to only run the diagnostics collection script without disturbing the container's original settings. By recreating the exact environment of the failed container, and running diagnostics on the environment, it is possible to obtain the log files from the original container as well as to implement diagnostic operations on the environment of the original container, which can then be used to help diagnose why the original container failed.