fix(notes): correct the URL to containerd-to-vm code

Change-Id: Ifcd265c515b0fc5e1999eed0d7594475e84a346a
Reviewed-on: https://cl.fcuny.net/c/world/+/413
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>

1 files changed, 1 insertions, 1 deletions

diff --git a/users/fcuny/notes/content/notes/containerd-to-firecracker.org b/users/fcuny/notes/content/notes/containerd-to-firecracker.org
index 554771d..cf00c03 100644
--- a/users/fcuny/notes/content/notes/containerd-to-firecracker.org
+++ b/users/fcuny/notes/content/notes/containerd-to-firecracker.org
@@ -15,7 +15,7 @@ They describe the process as follow:
 6. Create a TAP device and configure it
 7. Hand it off to Firecracker and boot that thing
 
-That's pretty detailed, and I'm curious how difficult it is to implement this. I've been meaning to look into Firecracker for a while and into containers'd API, so this is a perfect opportunity to get started. The code is available [[https://git.fcuny.net/fcuny/containerd-to-vm][here]].
+That's pretty detailed, and I'm curious how difficult it is to implement this. I've been meaning to look into Firecracker for a while and into containers'd API, so this is a perfect opportunity to get started. The code is available [[https://git.fcuny.net/world/tree/users/fcuny/exp/containerd-to-vm][here]].
 
 * #1 Pull a container from a registry with =containerd=
 =containerd= has a pretty [[https://pkg.go.dev/github.com/containerd/containerd][detailed documentation]]. From the main page we can see the following example to create a client.