Siemens Aktiengesellschaft

Christian Knierim

Christian Peter Feist

Angela Schattleitner

Jürgen Gessner

Various embodiments include an automated method for analyzing a container instance running on a host system in a runtime environment. The method may include: capturing an initial reference picture including a reproduction of the container instance; transferring the picture to a test system; capturing data when triggered by an event relating to an operation on the container instance; transmitting the data to the test system; producing an updated reference picture of the container instance by adjusting the initial reference picture for effects that the operations have on the container instance, the effects expected effects that the operations cause as expected; and analyzing the updated reference picture using the test system.

Analysis of a container instance of an operating system

Provided is a method for overload protection in a container-virtualized computing apparatus that provides a computer-implemented application by at least one work container, having the following steps: —receiving a request message to call the application, checking the currently existing workload of the computing apparatus against a stipulated load limit value, and if the current workload is higher than the load limit value, forwarding the request message to a load rejection container that provides at least one form of handling of the application that is modified compared to the work container.

Method for overload control in a container-virtualized computing apparatus

A method for securely starting up a container instance in one or more execution environments for one or more components of a technical installation, such an execution environment being designed to execute the container instance includes the following method steps:

Method and device for securely starting up a container instance

Provided is a method for orchestrating a container-based application that is executed on a terminal device, in which implementation information is received in an orchestration slave unit on the terminal device via a communication connection from an orchestration master unit, and the application is configured and/or controlled by the orchestration slave unit based on the implementation information, wherein the received implementation information is additionally saved persistently in a memory unit in the terminal device, and if the communication connection to the orchestration master unit is interrupted, the most recently saved implementation information is retrieved from the orchestration slave unit and the application is configured and/or controlled based on the most recently saved implementation information.

Orchestrating a container-based application on a terminal device

A method for expanded integrity monitoring of a container image, wherein the container image contains at least two layers, a base image and at least one application layer, which carries out at least one modification operation on the base image, includes the following steps: during assembly of the container image, allocating an integrity rule specific to the layer to the layer, for at least one of the layers of the container image, providing the container image and the allocated integrity rules to a guest computer, and—generating a container instance on the basis of the container image via a real-time environment of the guest computer, checking each individual layer in relation to the allocated integrity rules during execution of the container instance in the real-time environment, and—executing the layer according to the allocated layer-specific integrity rule.

Expanded integrity monitoring of a container image

A method is provided for storing at least one domain name system container image, wherein the domain name system container image is configured to create at least one domain name system container instance in a domain name system infrastructure. The method includes: creating at least one item of signed domain name system information, wherein the at least one item of signed domain name system information is created by a cryptographic signature of an item of domain name system information, wherein the cryptographic signature is created outside the domain name system server infrastructure; creating at least one domain name system container image, wherein the at least one domain name system container image has the signed domain name system information and at least one item of domain name system server software; and storing the at least one domain name system container image in a container registry.

Growing community of inventors

Munich, Germany

Christian Knierim