# Next Steps

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-kata/)
- [Explore Confidential Containers and Arm CCA attestation](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-kata/cca-kata/)
- [Run a confidential container with an encrypted image](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-kata/flow/)
- [Next Steps](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-kata/_next-steps/)

## Explore related resources
Find more information about the topics in this Learning Path:
- [Arm Confidential Compute Architecture](https://www.arm.com/architecture/security-features/arm-confidential-compute-architecture)
- [Arm Confidential Compute Architecture Open-Source enablement](https://www.youtube.com/watch?v=JXrNkYysuXw)
- [Learn the architecture - Realm Management Extension](https://developer.arm.com/documentation/den0126)
- [Realm Management Monitor Specification](https://developer.arm.com/documentation/den0137/latest/)
- [The Role of Attestation in Arm CCA](https://support.arm.com/documentation/111146/latest/)

## Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication.
Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

### How do I know the Trustee services are ready before pushing the image?
Confirm that the AS, KBS, and RVPS processes have started and are listening. Check their startup logs for ready or healthy messages before continuing.

### Which registry should I use when publishing the encrypted image?
Use the local Docker registry started as part of this Learning Path. Tag the encrypted image for that registry and push, and proceed only after the push completes without errors.

### What result should I expect when launching the confidential container on the FVP?
The runtime pulls the encrypted image from the local registry, performs Arm CCA attestation via Trustee, obtains decryption keys, and starts the workload inside an Arm CCA Realm. Expect logs indicating successful attestation or authorization and that the container is running.

### How can I verify the container is actually running inside an Arm CCA Realm?
Follow the verification step to check Realm-specific output from the launch. Validation relies on Trustee accepting CCA attestation evidence; without acceptance, the image remains locked and the workload does not start.

### What should I check if the encrypted image fails to pull or decrypt during launch?
Verify the local registry is running and reachable and that the image was pushed with the expected tag. Confirm AS, KBS, and RVPS are up and that attestation evidence is available so the KBS can release keys after authorization.
