-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AESM Error while executing Confidential PyTorch Example in Docker #82
Comments
@asim29 Thanks for the question! I think you'll also need to install the plugins of the AESM service (e.g., |
+1 to what @kailun-qin said. Also, to double-check whether the AESMD service is actually running, you can check for existence of this file: |
Thank you for the response! I included the plugins into my Dockerfile, and added the following lines:
I also made sure to restart the AESMD service, and the service itself seems to be working (i.e., the
I've installed the |
@asim29 Have you installed the PCCS service? See https://www.intel.com/content/www/us/en/developer/articles/guide/intel-software-guard-extensions-data-center-attestation-primitives-quick-install-guide.html Context: You need some service that constructs the Intel certificate chain for DCAP SGX Quotes. You can either install the PCCS service, or if you run on Microsoft Azure Confidential Computing VMs with SGX enabled, then it should be already set up to use Microsoft's own service. |
Hi @dimakuv, When I try to install the PCCS service, I get the following error:
I might need privileged access to the host machine I am running Docker on. A bit more context: I am trying to run this in a container on a Rootless Docker installation since I do not have root access to the host machine on which SGX is installed, and I do not have access to the system-wide Docker installation either. I have been trying to figure out how to run systemctl within a Docker container but haven't been able to do that; I get the error described in this StackOverflow post when I try to run systemctl. It seems this isn't recommended. Does the PCCS service need to be installed on the host machine? Is installing it in a Docker container running on a Rootless Docker installation possible? |
@asim29 It can be installed and run w/ a Docker container, pls take https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/master/QuoteGeneration/pccs/container as a reference. |
Hi! Thank you for the response. I have been trying to install PCCS within a Docker container using the Dockerfile as a reference, but I get an error with the When I try to build the referenced image as it is (the first step in the readme), I get the same error:
|
@asim29 Ah, this is a known issue. Pls kindly retry w/ the latest master branch of DCAP (as we just merged the fix: intel/SGXDataCenterAttestationPrimitives@b2b7eba). |
Thank you @kailun-qin I managed to install the PCSS server, and it seems to be working. The output of the command
However, the AESM service error I indicated earlier is still there. When I run the command
The only difference in the way I installed the PCCS server in my own Dockerfile is that I installed PCCS as the root user, rather than creating a new user for it (for simplicity's sake, I am not sure of the implications of this yet). Will that have potentially caused a problem? |
Hi, I am trying to run the end-to-end confidential pytorch example from this tutorial. I was able to run the non-confidential part of the tutorial using gramine-sgx, but I am running into the following error when trying to run the confidential example:
When I try to run
service aesmd status
I get the following output:I followed the tutorial and I can see that the
sgx-aesm-service
service is installed. The docker file I am using to run Gramine is:The manifest template (edited as shown in the tutorial):
I launch the provisioning server before I run the gramine commands and I can see it running in the background using the
top
command.I am unsure why the service command cannot find the aesmd service. I can see that the container does indeed contain the following files:
The aesmd.conf file looks like this:
Have I done something wrong in the installation process, or is something extra required to make this work within a Docker container?
I appreciate any help you can provide.
Best,
Asim.
The text was updated successfully, but these errors were encountered: