From fd3a6a3730d4078f6be4239a9c24c9747ef9d555 Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Tue, 31 Oct 2023 13:48:54 +0100 Subject: Theme update --- content/posts/2021-12-25-running-golang-application-as-pid1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/posts/2021-12-25-running-golang-application-as-pid1.md') diff --git a/content/posts/2021-12-25-running-golang-application-as-pid1.md b/content/posts/2021-12-25-running-golang-application-as-pid1.md index e09bbc9..d4db07d 100644 --- a/content/posts/2021-12-25-running-golang-application-as-pid1.md +++ b/content/posts/2021-12-25-running-golang-application-as-pid1.md @@ -23,7 +23,7 @@ Really worth a read. If we compare a normal operating system to a unikernel side by side, they would look something like this. -![Virtual machines vs Containers vs Unikernels](/posts/pid1/unikernels.png) +![Virtual machines vs Containers vs Unikernels](/posts/pid1/unikernels.webp) From this image, we can see how the complexity significantly decreases with the use of Unikernels. This comes with a price, of course. Unikernels are hard -- cgit v1.2.3