> For the complete documentation index, see [llms.txt](https://www.sdv.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.sdv.guide/sdv101/part-c-building-blocks/building-blocks-of-an-sdv/service-oriented-architecture/container-runtimes.md).

# Container Runtimes

Container runtimes form the operational backbone of **Software-Defined Vehicles (SDVs)**, extending principles from internet infrastructure into the automotive domain. While containers already power modern cloud services, adapting them for automotive applications comes with unique challenges and requirements.

## Key Requirements for Automotive Container Runtimes

Key Requirements for Automotive Container Runtimes include Fast and Deterministic Startup Times, Resource Optimization and Enhanced Security and Efficient Updates:

1. **Fast and Deterministic Startup Times**: In vehicles, startup delays are unacceptable. Imagine unlocking a car and waiting several seconds for critical services like the vehicle experience interface to boot. Automotive-grade container runtimes must ensure near-instant responses, supporting real-time or near-real-time applications even within QM environments.
2. **Resource Optimization**: Onboard compute systems face hardware constraints despite using high-performance processors. Unlike cloud environments, onboard systems cannot scale elastically. Therefore, efficient resource allocation is essential, ensuring that containerized services run smoothly within limited computational resources.
3. **Enhanced Security and Efficient Updates**: Automotive containers require robust security measures, such as isolation between services, secure boot mechanisms, and protection against cyber threats. Efficient update mechanisms must support seamless over-the-air (OTA) updates with minimal downtime.

## Container Runtimes in Automotive E/E Architecture

In an automotive **E/E architecture**, container runtimes fit within the broader system structure, enabling flexible and scalable service deployment:

* **Central Compute Unit**: This unit hosts multiple instances of operating systems, often using virtualization technologies like hypervisors.
* **Virtual OS Instances**: Inside these virtual machines, container runtimes manage microservice deployment.
* **Container Runtimes**: Lightweight and modular, these environments host one or more microservices, creating a service-oriented architecture.
* **Microservices**: Each microservice runs independently, providing modular vehicle functionalities. Multiple containerized services can run simultaneously, ensuring robust and scalable performance.

<figure><img src="/files/EmqWKLqukWM9mJdBPLhS" alt=""><figcaption></figcaption></figure>

By integrating container runtimes, **Software-Defined Vehicles** achieve the scalability, modularity, and reliability needed for modern automotive functions while ensuring seamless interaction with **off-board cloud services**. This combination enables **real-time applications**, **over-the-air updates**, and **enhanced service delivery**, forming the technological backbone of next-generation automotive platforms.