In some use cases, such as with Confidential Containers or Peer-Pods, a longer ContainerCreateTimeout is necessary. For instance, when deploying a Peer-Pod using a cloud instance with a long startup time, such as DGX-like systems, the current hardcoded timeout of 240 seconds may be exceeded before the container’s hosting VM completes its initialization.

To support such scenarios, it would be helpful to either make ContainerCreateTimeout configurable via the CRI-O configuration file or consider increasing the default value.