vault backup: 2025-08-16 11:14:58

.obsidian/workspace.json

@@ -13,12 +13,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "5 - People/Insa Sangs.md",
+                "file": "temporary.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "Insa Sangs"
+              "title": "temporary"
             }
           }
         ]
@@ -171,6 +171,10 @@
   },
   "active": "b9dd396163cf054d",
   "lastOpenFiles": [
+    "5 - People/Insa Sangs.md",
+    "Computer Science Education.md",
+    "CS 2025 Education planning.md",
+    "6 - Journal/2025-08-10.md",
     "3 - Resources/Silkroad Pserver.md",
     "3 - Resources/Silkroad Online.md",
     "temporary.md",

temporary.md

@@ -19,3 +19,18 @@ For a weak, dont do things you know are vad and do things you know are good for
 
 Learn traffic rules
 Earn IBM Fullstack developer certificate (but afte)
+
+
+- ctr: CLI for containerD, not very user friendly and mostly for debugging
+	- It is advised to use nerdctl instead
+- nerdctl: provides docker-like CLI for containerd, supports docker compose, supports newest features in containerD (encrypted container images, lazy pulling...)
+- crictl: provides a CLI for CRI-compatible container runtimes, installed separately, used to inspect and debug container runtimes (not to create containers ideally), works across different runtimes
+	- `crictl pods` shows pods
+	- `crictl --runtime endpoint` enables you to specify a runtime endpoint (or use CONTAINER_RUNTIME_ENDPOINT env var)
+	- other commands are similar to docker
+## Glossary
+- CRI: Container Runtime Interface
+	- Kubernetes originally only worked for Docker but then introduced the CRI to be more abstract and allow all sorts of container runtimes
+- OCI: Open Container Initiative
+	- imagespec: specification on how an image should be build
+	- runtimespec: standards on how a container runtime shall be deployed