diff --git a/assets/images/cgroups.png b/assets/images/cgroups.png
new file mode 100644
index 0000000..4c4f2a5
Binary files /dev/null and b/assets/images/cgroups.png differ
diff --git a/assets/images/docker-filesystem.png b/assets/images/docker-filesystem.png
new file mode 100644
index 0000000..5b98924
Binary files /dev/null and b/assets/images/docker-filesystem.png differ
diff --git a/categories/devops/docker.md b/categories/devops/docker.md
index 37b22d2..7fa9ab1 100644
--- a/categories/devops/docker.md
+++ b/categories/devops/docker.md
@@ -36,6 +36,9 @@ Docker Engine uses the following namespaces on Linux:
 
 ### Cgroups
 
+![cgroups](https://raw.githubusercontent.com/wahyd4/knowledge-mind-mapping/master/assets/images/cgroups.png)
+
+
 Docker also makes use of kernel control groups for resource allocation and isolation. A cgroup limits an application to a specific set of resources. Control groups allow Docker Engine to share available hardware resources to containers and optionally enforce limits and constraints.
 Docker Engine uses the following cgroups:
 
@@ -50,6 +53,9 @@ Docker Engine uses the following cgroups:
 
 ### Union File Systems
 
+![filesystem](https://raw.githubusercontent.com/wahyd4/knowledge-mind-mapping/master/assets/images/docker-filesystem.png)
+
+
 Union file systems operate by creating layers, making them very lightweight and fast. Docker Engine uses UnionFS to provide the building blocks for containers. Docker Engine can use multiple UnionFS variants, including AUFS, btrfs, vfs, and devicemapper.
 
 ### Container Format