A host computer inventory system within a provider network detects patterns of launch requests on an individual user account basis. For a customer that cyclically submits similar launch requests, the inventory system may allocate slots in specific host computers consistent with the detected launch pattern so that future attempts to launch the virtual machines will be honored using the pre-allocated hosts.

A software operator can be automatically configured and deployed in a distributed computing environment from a package. For example, a system can receive a command specifying a package for deploying a target operator. In response to receiving the command, the system can automatically configure and deploy the target operator in a computing cluster. This may involve the system extracting a name for the target operator from the corresponding package and assigning an operator group to the target operator. The system can then subscribe the target operator to an operator management system by indicating the name and a namespace of the operator group to one or more application programming interfaces of the computing cluster. The system can also deploy an instance of the target operator in the namespace on the computing cluster.

A method for providing container images in a distributed computing system is presented. The method includes the following: uploading a user Dockerfile via a management application; uploading Dockerfile metadata via the management application; providing the Dockerfile to a Docker container image builder to create a Docker container image; receiving, at an application store, the Docker container image from the Docker container image builder; providing the Dockerfile metadata to the application store; presenting, from the application store, the Docker container image; and providing, based on a user selection, the Docker container image to one of a plurality of third-party compute systems.

Systems and methods for container orchestration security employ one or more processors that separate a lifecycle of one or more containers into a plurality of predefined container image lifecycle phases; segregates control of the plurality of predefined container image lifecycle phases into a plurality of control environments separately controlled by different enterprise control components isolated from one another. In addition, one or more external processors may generate one or more certificates that are based on the platform, state attributes and meta data for interaction of the container with one or more external nodes. The one or more processors may also control the promotion, update and deletion of container images between the plurality of lifecycle phases and registries in different control environments as well as between the enterprise registries and the plurality of other registries that are part of multiple external clouds.

A container stack configurator can build customized software applications and deploy the applications to a wellbore computing network or through offline installer devices. The stack configurator can receive a selection from a user of a configuration repository. The stack configurator can determine available branches of the configuration repository including images, tags, and container names. The stack configurator can present a list of services associated with the container names to the user using a user interface. The stack configurator can receive a selection of an installer type and generate a customized build of the installer type. The customized build of the installer can be an offline installer that is deployable on an offline target machine using a first communication media or an online installer that is deployable to an online target machine using a second communication media.

Various examples are directed to systems and methods for installing a plugin to a cloud-implemented database management application. A shared container file system may be initiated at a cloud environment. A plugin container image maybe accessed, where the plugin container image comprises plugin payload data describing a first plugin to the database management application and a copy executable. A plugin container may be started at the cloud environment, where the plugin container is based at least in part on the plugin container image. The plugin container may be mounted to the shared container file system. The copy executable may be executed to copy the plugin payload data to the shared container file system. The first plugin may be installed to a database management application instance executing at the cloud environment.

Building images that enable improved utilization of previously built image layers. An image build system evaluates commands prior to their use and differentiate between stateful and stateless commands. Employing such an approach enables stateless commands to be identified (e.g. labeled), thus enabling the image build system to handle the stateless commands differently from stateful commands. This enables the re-use of cached/stored image layers, thus reducing image size by avoiding the creation of new image layers.

A method of creating a software image of a solution to be deployed in a virtualized computing environment includes: retrieving a schema of the solution and determining from the schema software products that are required by the solution and software features that are required by the solution; for each software product, selecting a version of the software product to include in the solution and identifying software features provided by the selected version of the software product; and upon confirming that the selected versions of the software products provide all of the software features that are required, creating the software image of the solution that includes the selected version of each of the software products, and saving the software image in a storage device for deployment in the virtualized computing environment.

Generally described, one or more aspects of the present application relate to prefetching container images for use in a cluster of virtual machines. For example, the cluster manifest may indicate an ordered list of image repositories and a set of container images that are likely to be executed on the cluster. Based on this indication, the set of container images can be prefetched onto the caches of the virtual machines in the cluster, such that when requests to execute those container images are eventually received, the container images can be accessed from the caches rather than from a remote repository.

Various examples described herein are directed to systems and methods for managing a cloud-implemented database management application, the method comprising. At least one cloud service may receive a request from a first user group to launch a first instance of the database management application. The at least one cloud service may access a version metadata record for the database management application and use the version metadata record to launch the first instance of the database management application. The at least one cloud service may store first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application. The first instance metadata may comprise an indication of the first container image.