From 91a6a0ce8aff5e09cafa6322abb6a44dcdf828cf Mon Sep 17 00:00:00 2001 From: Zalan Blenessy Date: Mon, 1 Jul 2024 09:07:45 +0200 Subject: [PATCH] dev-docs: fix links in life-of-a-confidential-container.md --- dev-docs/aks/life-of-a-confidential-container.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dev-docs/aks/life-of-a-confidential-container.md b/dev-docs/aks/life-of-a-confidential-container.md index 6d29302fcb..963e626722 100644 --- a/dev-docs/aks/life-of-a-confidential-container.md +++ b/dev-docs/aks/life-of-a-confidential-container.md @@ -119,7 +119,7 @@ spec: We use the [`genpolicy`] tool to generate a runtime policy for the pod. This policy defines what OCI runtime parameters are acceptable for this pod. -Runtime policies are covered in more detail in a [dedicated document](../coco/policy). +Runtime policies are covered in more detail in a [dedicated document](../coco/policy.md). It also calculates a `dm-verity` hash, but more on that later. [`genpolicy`]: https://github.com/microsoft/kata-containers/tree/3.2.0.azl1.genpolicy0/src/tools/genpolicy @@ -339,7 +339,7 @@ curl -s --unix-socket /run/vc/vm/6aa04b0c9483817bb9da7216c352348d33d6fda1ecd10ac ## Kata Agent Inside the confidential VM, the Kata Agent starts up and serves the [agent API]. -If we configured Kata for [debug mode](serial-console), we can log into the container by sandbox id: +If we configured Kata for [debug mode](serial-console.md), we can log into the container by sandbox id: ```sh kata-runtime exec 6aa04b0c9483817bb9da7216c352348d33d6fda1ecd10ac5c836bcd4a1652bed