Simply Explained: Containerisation in RDK-B

Let’s explore the fundamentals of containerisation in RDK-B — from security and flexibility benefits to lifecycle management with DSM and Dobby components. Learn how containers enable modular, resilient, and future-ready broadband devices and how they can even enhance legacy hardware.

What is RDK-B?

RDK-B (Reference Design Kit for Broadband) is an embedded Linux environment that powers home broadband devices like routers. It provides a standardised framework, making building and maintaining products easier for multiple vendors.

What is Containerisation in RDK-B?

Think of a container as a self-contained environment that runs inside the main system but remains isolated from it. In RDK-B devices, containers can operate independently, with their own libraries, dependencies, and configurations — while still sharing critical resources like the kernel.

Why does it matter?

• Security: Containers isolate applications, reducing the risk of crashes and vulnerabilities affecting the whole system. Even if an app fails, your RDK-B device keeps running smoothly.
• Flexibility: Containers allow you to run specific software versions without risking conflicts across the system. Perfect for legacy apps that need an older Python version, for instance.
• Efficiency: Updates and rollbacks are streamlined, minimising downtime and security risks. Plus, uninstalling a container doesn’t leave behind unwanted dependencies.
• Application and Service Management: Using components like DSM (Device Software Module) and Dobby (Docker-based execution engine), RDK-B provides robust tools for installing, upgrading, and managing containers easily and securely.

The bigger picture

Containerisation opens the door for exciting new services, like integrated firewalls, smart home controllers, ad blockers, and even antivirus software — all running directly on your smart broadband router. And it’s not just for cutting-edge hardware — containers can breathe new life into legacy devices too.