diff --git a/src/data/roadmaps/linux/content/116-containerization/102-container-runtime.md b/src/data/roadmaps/linux/content/116-containerization/102-container-runtime.md
index 73df89b08..f0ad1fa7c 100644
--- a/src/data/roadmaps/linux/content/116-containerization/102-container-runtime.md
+++ b/src/data/roadmaps/linux/content/116-containerization/102-container-runtime.md
@@ -8,9 +8,4 @@ Under Linux, popular container runtime options include:
 - Containerd: Originally developed as a high-level container runtime layer to be used in Docker, Containerd is now often used as a standalone runtime.
 - CRI-O: A lightweight container runtime specifically optimized for Kubernetes.
 
-```bash
-# Sample command to start a Docker container 
-docker run -d -p 80:80 docker/getting-started
-```
-
 In containerization, understanding the role of container runtime is integral as it helps in better designing and running your containerized applications. This further ensures reliability and efficient use of resources. Each container runtime can be suited for different use cases so it's best to understand their pros and cons to use them effectively.
\ No newline at end of file