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
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,7 +143,9 @@ spec:
143
143
alibabacloud.com/sgx_epc_MiB: 20
144
144
```
145
145
146
-
If you want a remote attestation, you should mount `/var/run/aesmd/aesm.socket` in your container, maybe like this:
146
+
If you want a remote attestation, aesm.socket MUST BE mounted inside application containers. There are two ways to achieve it:
147
+
148
+
Way 1: Mount aesm.socket (i.e. /var/run/aesmd/aesm.socket) inside your application containers manually, maybe like this:
147
149
148
150
```yaml
149
151
apiVersion: v1
@@ -172,6 +174,8 @@ spec:
172
174
173
175
```
174
176
177
+
Way 2: Enable AESM socket attachment of sgx-device-plugin (via --enable-aesm-socket-attach=true) which will help you mount ASEM socket inside your application containers automatically. See deploy/sgx-device-plugin-enable-aesm.yml.
178
+
175
179
## FAQ
176
180
177
181
***Can I deploy this SGX device plugin in my own self-hosting Kubernetes?**
0 commit comments