Switch to quay.io

Author: jason-fox

.env

@@ -3,14 +3,14 @@ COMPOSE_PROJECT_NAME=fiware
 
 # Orion variables
 ORION_PORT=1026
-ORION_VERSION=3.7.0
+ORION_VERSION=3.8.1
 
 # MongoDB variables
 MONGO_DB_PORT=27017
 MONGO_DB_VERSION=4.4
 
 # IoT Agent JSON Variables
-JSON_VERSION=1.25.0-distroless
+JSON_VERSION=2.0.0-distroless
 IOTA_NORTH_PORT=4041
 IOTA_SOUTH_PORT=7896
 

FIWARE IoT Agent JSON.postman_collection.json

@@ -274,7 +274,7 @@ IoT デバイスと IoT Agent を接続するために必要な設定情報は
 
 ```yaml
 tutorial:
-    image: fiware/tutorials.context-provider
+    image: quay.io/fiware/tutorials.context-provider
     hostname: iot-sensors
     container_name: fiware-tutorial
     networks:
@@ -332,7 +332,7 @@ YAML ファイルで説明されている他の `tutorial` コンテナ設定値
 
 ```yaml
 iot-agent:
-    image: fiware/iotagent-json:latest
+    image: quay.io/fiware/iotagent-json:latest
     hostname: iot-agent
     container_name: fiware-iot-agent
     depends_on:
@@ -641,7 +641,7 @@ Context Broker に渡す必要があります。`entity_type` 属性は、リク
 ### センサのプロビジョニング
 
 エンティティを作成するときは、
-NGSI-LD [仕様](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.04.01_60/gs_cim009v010401p.pdf)
+NGSI-LD [仕様](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf)
 に従って URN を使用することをお勧めします。さらに、データ属性を定義する
 ときに意味のある名前を理解する方が簡単です。これらのマッピングは、
 デバイスを個別にプロビジョニングすることで定義できます。

README.ja.md

@@ -229,7 +229,7 @@ section of the associated `docker-compose.yml` file:
 
 ```yaml
 tutorial:
-    image: fiware/tutorials.context-provider
+    image: quay.io/fiware/tutorials.context-provider
     hostname: iot-sensors
     container_name: fiware-tutorial
     networks:
@@ -280,7 +280,7 @@ tagged `fiware/iotagent-json`. The necessary configuration can be seen below:
 
 ```yaml
 iot-agent:
-    image: fiware/iotagent-json:latest
+    image: quay.io/fiware/iotagent-json:latest
     hostname: iot-agent
     container_name: fiware-iot-agent
     depends_on:
@@ -535,7 +535,7 @@ however it has been included here for completeness.
 ### Provisioning a Sensor
 
 It is common good practice to use URNs following the NGSI-LD
-[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.04.01_60/gs_cim009v010401p.pdf) when creating
+[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf) when creating
 entities. Furthermore it is easier to understand meaningful names when defining data attributes. These mappings can be
 defined by provisioning a device individually.
 

README.md

@@ -22,7 +22,7 @@ services:
   orion:
     labels:
       org.fiware: 'tutorial'
-    image: fiware/orion:${ORION_VERSION}
+    image: quay.io/fiware/orion:${ORION_VERSION}
     hostname: orion
     container_name: fiware-orion
     depends_on:
@@ -40,7 +40,7 @@ services:
 
   # IoT-Agent is configured for the JSON Protocol
   iot-agent:
-    image: fiware/iotagent-json:${JSON_VERSION}
+    image: quay.io/fiware/iotagent-json:${JSON_VERSION}
     hostname: iot-agent
     container_name: fiware-iot-agent
     depends_on:
@@ -77,7 +77,7 @@ services:
   tutorial:
     labels:
       org.fiware: 'tutorial'
-    image: fiware/tutorials.context-provider
+    image: quay.io/fiware/tutorials.context-provider
     hostname: iot-sensors
     container_name: fiware-tutorial
     depends_on: