You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Components in Dstack:
26
26
-`teepod`: A service running in bare TDX host to manage CVMs
27
27
-`tproxy`: A reverse proxy to forward TLS connections to CVMs
28
28
-`kms`: A KMS server to generate keys for CVMs
29
-
-`tappd`: A service running in CVM to serve containers' key derivation and attestation requests
29
+
-`dstack-guest-agent`: A service running in CVM to serve containers' key derivation and attestation requests
30
30
-`meta-dstack`: A Yocto meta layer to build CVM guest images
31
31
32
32
The overall architecture is shown below:
@@ -37,7 +37,7 @@ The overall architecture is shown below:
37
37
```text
38
38
dstack/
39
39
kms/ A prototype KMS server
40
-
tappd/ A service running in CVM to serve containers' key derivation and attestation requests.
40
+
guest-agent/ A service running in CVM to serve containers' key derivation and attestation requests.
41
41
tdxctl/ A CLI tool getting TDX quote, extending RTMR, generating cert for RA-TLS, etc.
42
42
teepod/ A service running in bare TDX host to manage CVMs
43
43
tproxy/ A reverse proxy to forward TLS connections to CVMs
@@ -151,7 +151,7 @@ After the container deployed, it should need some time to start the CVM and the
151
151
152
152
- Once the container is running, you can click the [Dashboard] button to see some information of the container. And the logs of the containers can be seen in the [Dashboard] page.
0 commit comments