Merge pull request #3463 from Arnaud-de-Grandmaison-ARM/cca-images-update

[CCA] Update docker images for various learning paths.

Author: pareenaverma

content/learning-paths/servers-and-cloud-computing/cca-device-attach/4.lab-observe-bounce-buffers.md

@@ -15,8 +15,8 @@ In this exercise, you’ll run the CCA Key Broker demo inside a Realm and use ke
 Pull the Docker container image with the pre-built KBS, and run the container:
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-key-broker-v2 
-docker run --rm -it armswdev/cca-learning-path:cca-key-broker-v2
+docker pull armlimited/cca-learning-path:cca-key-broker-v4
+docker run --rm -it armlimited/cca-learning-path:cca-key-broker-v4
 ```
 
 List network interfaces:
@@ -62,8 +62,8 @@ which you will run the Key Broker Client (KBC). The intent is to confirm that th
 Pull the Docker container image with the pre-built KBC, and then run the container:
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-simulation-v2
-docker run --rm -it armswdev/cca-learning-path:cca-simulation-v2
+docker pull armlimited/cca-learning-path:cca-simulation-v4
+docker run --rm -it armlimited/cca-learning-path:cca-simulation-v4
 ```
 
 Launch the Arm CCA prebuilt binaries on the FVP:

content/learning-paths/servers-and-cloud-computing/cca-essentials/example.md

@@ -21,8 +21,8 @@ The KBS in this Learning Path is part of the [Veraison](https://github.com/verai
 First, pull the docker container image with the pre-built KBS, and then run the container:
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-key-broker-v2
-docker run --rm -it armswdev/cca-learning-path:cca-key-broker-v2
+docker pull armlimited/cca-learning-path:cca-key-broker-v4
+docker run --rm -it armlimited/cca-learning-path:cca-key-broker-v4
 ```
 
 Now within your running docker container, get a list of network interfaces:
@@ -66,12 +66,12 @@ With the Key Broker Server running in one terminal, open up a new terminal in wh
 In the new terminal that you have just opened, pull the docker container image that contains the FVP and pre-built software binaries to run the Key Broker Client in a realm.
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-simulation-v2
+docker pull armlimited/cca-learning-path:cca-simulation-v4
 ```
 
 Now run the docker container:
 ```bash
-docker run --rm -it armswdev/cca-learning-path:cca-simulation-v2
+docker run --rm -it armlimited/cca-learning-path:cca-simulation-v4
 ```
 
 Within your running container, launch the `run-cca-fvp.sh` script to run the Arm CCA pre-built binaries on the FVP:

content/learning-paths/servers-and-cloud-computing/cca-kata/flow.md

@@ -149,10 +149,10 @@ With the Trustee services running in one terminal, open a second terminal for th
 Pull the pre-built FVP container image and run it on the same Docker network:
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-simulation-with-kata-v3
+docker pull armlimited/cca-learning-path:cca-simulation-with-kata-v4
 ```
 ```bash
-docker run --rm -it --network cca-trustee armswdev/cca-learning-path:cca-simulation-with-kata-v3
+docker run --rm -it --network cca-trustee armlimited/cca-learning-path:cca-simulation-with-kata-v4
 ```
 
 Inside your running container, launch the `run-cca-fvp.sh` script to run the Arm CCA pre-built binaries on the FVP:

content/learning-paths/servers-and-cloud-computing/cca-trustee/flow.md

@@ -88,10 +88,10 @@ With the Trustee Services running in one terminal, open up a new terminal in whi
 Pull the Docker image with the pre-built FVP, and then run the container connected to the same Docker network:
 
 ```bash
-docker pull armswdev/cca-learning-path:cca-simulation-v2
+docker pull armlimited/cca-learning-path:cca-simulation-v4
 ```
 ```bash
-docker run --rm -it --network cca-trustee armswdev/cca-learning-path:cca-simulation-v2
+docker run --rm -it --network cca-trustee armlimited/cca-learning-path:cca-simulation-v4
 ```
 
 Within your running container, launch the `run-cca-fvp.sh` script to run the Arm CCA pre-built binaries on the FVP:
@@ -285,7 +285,7 @@ Configuration [none]: no claim being made
 Executables [affirming]: recognized and approved boot-time
 File System [none]: no claim being made
 Hardware [affirming]: genuine
-Runtime Opaque [none]: no claim being made
+Runtime Opaque [affirming]: memory encryption
 Storage Opaque [none]: no claim being made
 Sourced Data [none]: no claim being made
 ```