The high-level steps for containerizing your My webMethods Server installation are as follows:

When you use the Docker command line to create a new container from a My webMethods Server image, My webMethods Server uses a dedicated startup script to start a server instance inside the container. You can use environment variables to pass specific configurations to the startup script to override the predefined settings from the Docker image, for example to start My webMethods Server with a different database than the database, used by the instance from the image, or to redirect the server logs to a different storage location. For more information about the environment variables for My webMethods Server, see About the My webMethods Server Environment Variables

When starting up in a container, My webMethods Server performs a series of additional validation checks such as database connectivity, database integrity, and volume consistency checks. If any of the validation checks fails, the container exits. Unless you redirect the server logs to another location, logs are available on the console or in the default volumes that Docker creates for My webMethods Server. For more information about the default volumes, see Managing Assets and Data in My webMethods Server Containers