Update Manager is not working

[AhmedElkazzaz]

I used the example in
https://eclipse.dev/kanto/docs/references/update-manager/update-manager-api/
{
"topic":"edge/device/things/live/messages/apply",
"headers":{
"response-required":true,
"content-type":"application/json",
"correlation-id":""
},
"path":"/features/UpdateManager/inbox/messages/apply",
"value":{
"activityId": "d91ad6fe-9b0c-4549-bf31-17d0a71b61de",
"desiredState": {
"baselines": [
{
"title": "simple-baseline",
"description": "",
"precondition": "",
"components": [
"domain:component1",
"domain:component2"
]
}
],
"domains": [
{
"id": "containers",
"config": [
{
"key": "source",
"value": "value"
}
],
"components": [
{
"id": "containers:influxdb",
"version": "2.7.1",
"config": [
{
"key": "image",
"value": "docker.io/library/influxdb:$influxdb_version"
}
]
}
]
}
]
}
}
}

I published this message from AWS and I could receive it on my Raspberrypi but nothing happened.
No new container is created !

mosquitto_sub -h localhost -t "#" -v
edge/connection/remote/status {"connected":true,"timestamp":1745576998}
containersupdate/currentstate {"activityId":"initial-current-state-1745576976829","timestamp":1745576976830,"payload":{"softwareNodes":[{"id":"containers-update-agent","version":"1.0.0","name":"Eclipse Kanto Containers Update Agent","parameters":[{"key":"domain","value":"containers"}],"type":"APPLICATION"}]}}
command//edge:mydevice/req//apply {
"topic":"edge/mydevice/things/live/messages/apply",
"headers":{
"response-required":true,
"content-type":"application/json",
"correlation-id":"7443986c-cb3a-4ca7-830b-a57970c495a2"
},
"path":"/features/UpdateManager/inbox/messages/apply",
"value":{
"activityId": "d91ad6fe-9b0c-4549-bf31-17d0a71b61de",
"desiredState": {
"baselines": [
{
"title": "simple-baseline",
"description": "",
"precondition": "",
"components": [
"domain:component1",
"domain:component2"
]
}
],
"domains": [
{
"id": "containers",
"config": [
{
"key": "source",
"value": "value"
}
],
"components": [
{
"id": "containers:influxdb",
"version": "2.7.1",
"config": [
{
"key": "image",
"value": "docker.io/library/influxdb:$influxdb_version"
}
]
}
]
}
]
}
}
}
c//edge:mydevice/q//apply {
"topic":"edge/mydevice/things/live/messages/apply",
"headers":{
"response-required":true,
"content-type":"application/json",
"correlation-id":"7443986c-cb3a-4ca7-830b-a57970c495a2"
},
"path":"/features/UpdateManager/inbox/messages/apply",
"value":{
"activityId": "d91ad6fe-9b0c-4549-bf31-17d0a71b61de",
"desiredState": {
"baselines": [
{
"title": "simple-baseline",
"description": "",
"precondition": "",
"components": [
"domain:component1",
"domain:component2"
]
}
],
"domains": [
{
"id": "containers",
"config": [
{
"key": "source",
"value": "value"
}
],
"components": [
{
"id": "containers:influxdb",
"version": "2.7.1",
"config": [
{
"key": "image",
"value": "docker.io/library/influxdb:$influxdb_version"
}
]
}
]
}
]
}
}
}

sudo kanto-cm list
No containers found.
ahmed@raspberrypi:~ $

[AhmedElkazzaz]

Any update ?

[chheis]

Hi @AhmedElkazzaz can you start the shell with command: mosquitto_sub -h localhost -t "#" -v before you send the Update command from AWS?
Did you follow this guide at least once?
https://eclipse.dev/kanto/docs/how-to-guides/update-software-um/

BTW: Pay attention to spaces within the mqtt topics (this happend to me while copying sometimes)

[AhmedElkazzaz]

I tried the example here
https://eclipse.dev/kanto/docs/how-to-guides/update-software-um/
and it worked before ,but what I need now is to create and update container directly with mqtt messages from AWS cloud without using the Eclipse Hono scripts .
How can I achieve that ?

[chheis]

Yeah, you need to send a specific format (json) via MQTT). There is a tutorial here at the Eclipse Leda project: https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/ explaining the concept visually, and what you need to send via MQTT to update e.g. a container you can find here: https://eclipse-leda.github.io/leda/docs/device-provisioning/container-management/container-update-agent/
And what you like to do is (as far as I understood it): Sending an MQTT message with a new desired state (json format) from AWS (python script) to your device running an kanto update manager + kanto container manager. So there is an example with azure: https://eclipse-leda.github.io/leda/docs/device-provisioning/container-management/cloud-connectivity/
But it would be as simple as this command:
mosquitto_pub -t containersupdate/desiredstate -f leda-desired-state.json
(after you created the leda-desired-state.json file) e.g. modify this one here: https://eclipse-leda.github.io/leda/docs/device-provisioning/container-management/leda-desired-state.json

And last but not least my dear @konstantina-gramatova had made a wonderful YouTube video for alle the things you should know about kanto: https://www.youtube.com/watch?v=bMN_ZiUS3Bc

Hope that helps. :)

[chheis]

Ahh and have a look in the logs of the kanto-cm and the update-manager! You can read them out with cat
Or may you try to run this tool:
https://github.com/eclipse-leda/leda-utils/tree/main/src/rust/kanto-tui

[AhmedElkazzaz]

Should I use Eclipse Leda Image ?
I was trying to work only with Eclipse Kanto on my Raspberry pi and I followed the update manager documentation
https://eclipse.dev/kanto/docs/references/update-manager/update-manager-api/

[chheis]

This should work on you RPI with nearly any distro. Eclipse Leda is a yocto build image with no packagemanager on it. So if you want to use it for an embedded device it would be beneficial. But not if you "just" want to use kanto.
You can try out to download and flash the Leda image, but building it yourself you should avoid currently, I think the current build will break. Maybe due to missing update maintenance/security build warnings.

Did you check the kanto-cm logs and the update manager logs?

Btw: you can also use Eclispe ANKAIOS: https://github.com/eclipse-sdv-blueprints/software-orchestration
Here you find a Blueprint for is in the Eclipse SDV Blueprints project

[AhmedElkazzaz]

he Update Manager identifies and acknowledges container creation requests via MQTT (containersupdate/desiredstatefeedback shows IDENTIFIED status with "New container will be created and started"), but no container is actually created. The Container Management service logs show no errors or relevant activity during this process.

sudo cat config.json
{
"caCert": "/etc/aws-connector/AmazonRootCA1.pem",
"cert": "/etc/aws-connector/mydevice.crt",
"key": "/etc/aws-connector/mydevice.key",
"address": "tls://xxxxxxxxxxxxxxxxxxx-ats.iot.eu-central-1.amazonaws.com:8883",
"tenantId": "webasto",
"deviceId": "mydevice",
"clientId": "webasto:mydevice",
"logFile": "/var/log/aws-connector/aws-connector.log",
"logLevel": "DEBUG",
"localAddress": "tcp://192.168.100.11:1883"
}
ahmed@raspberrypi:/etc/aws-connector $

cat /etc/container-management/config.json
{
"things": {
"enable": true,
"features": ["ContainerFactory", "SoftwareUpdatable", "Metrics"]
},
"update_agent": {
"enable": true,
"domain": "containers",
"system_containers": [
"someip-provider",
"my-databroker",
"databroker-cli",
"my-node-red"
]
},
"connection": {
"broker_url": "tcp://192.168.100.11:1883"
},
"log": {
"log_file": "/var/log/container-management/container-management.log",
"log_level": "DEBUG"
}
}
ahmed@raspberrypi:~ $

---

Published desired state via MQTT:

bash
mosquitto_pub -h 192.168.100.11 -t containersupdate/desiredstate -f nginx-only.json
Where nginx-only.json contains:

json
{
"activityId": "create-nginx-test",
"payload": {
"domains": [{
"id": "containers",
"components": [{
"id": "nginx-container",
"version": "1.0.0",
"config": [
{"key": "image", "value": "docker.io/library/nginx:1.27.5-alpine3.21"},
{"key": "port", "value": "8080:80/tcp"},
{"key": "restartPolicy", "value": "always"}
]
}]
}]
}
}

Observed feedback:
mosquitto_sub -h 192.168.100.11 -t containersupdate/desiredstatefeedback -v
containersupdate/desiredstatefeedback {"activityId":"create-nginx-test","timestamp":1750977539073,"payload":{"status":"IDENTIFYING"}}
containersupdate/desiredstatefeedback {"activityId":"create-nginx-test","timestamp":1750977539074,"payload":{"status":"IDENTIFIED","actions":[{"component":{"id":"containers:nginx-container","version":"1.0.0"},"status":"IDENTIFIED","message":"New container will be created and started."}]}}

---

Expected Behavior:

Nginx container should be created and appear in sudo kanto-cm list

Container Management logs should show creation/pull events

Actual Behavior:

No container created

No relevant log entries in Container Management (journalctl -u container-management)

Update Manager feedback stops at IDENTIFIED status

[AhmedElkazzaz]

Hello
Is there any updates regarding the issue ?
Is the problem from my side ? I am doing something not correct or the update manager is not working ?

[chheis]

Hi @AhmedElkazzaz was on vacation. Did you try to get the container image manually with the cli of kanto-cm?
Here you find an example command.
https://eclipse-leda.github.io/leda/docs/app-deployment/kuksa-databroker/
kanto-cm create --i --t --network=host --name=databroker-cli ghcr.io/eclipse/kuksa.val/databroker-cli:master

I think there is maybe the credentials for the docker.io container repo missing.
Did you install an Eclipse Mosquitto MQTT broker locally?

[AhmedElkazzaz]

Hello Chheis,

No worries and welcome back !
Yes I have created the cli using your command and I have Eclipse Mosquitto MQTT broker locally installed :

740b272f-80f3-472b-ab6b-a78e0580bf0e |my-databroker |ghcr.io/eclipse-kuksa/kuksa-databroker:latest |Running |2025-07-14T23:28:55.930537874Z |0 |
d2163820-fefb-42ef-9309-60cce655e435 |databroker-cli |ghcr.io/eclipse/kuksa.val/databroker-cli:master |Running | |0 |

---

But I still have the same problem
mosquitto_sub -h 192.168.100.11 -t containersupdate/desiredstatefeedback -v
containersupdate/desiredstatefeedback {"activityId":"create-nginx-test","timestamp":1752571093506,"payload":{"status":"IDENTIFYING"}}
containersupdate/desiredstatefeedback {"activityId":"create-nginx-test","timestamp":1752571093507,"payload":{"status":"IDENTIFIED","actions":[{"component":{"id":"containers:nginx-container","version":"1.0.0"},"status":"IDENTIFIED","message":"New container will be created and started."},{"component":{"id":"containers:my-databroker","version":"latest"},"status":"IDENTIFIED","message":"Existing container will be destroyed, no longer needed."},{"component":{"id":"containers:databroker-cli","version":"master"},"status":"IDENTIFIED","message":"Existing container will be destroyed, no longer needed."},{"component":{"id":"containers:my-node-red","version":"main"},"status":"IDENTIFIED","message":"Existing container will be destroyed, no longer needed."}]}}

It shows me Existing container will be destroyed and New container will be created ,but neither destroying nor creating happened .

[chheis]

than there must be something wrong with your container manager config or your update manager. Are they both connected to the same MQTT broker adress? Are they listening to the same topics?

[chheis]

otherwise try downloading the Eclipse Leda QEmu Image an try it with that. https://eclipse-leda.github.io/leda/docs/general-usage/running-qemu/
https://github.com/eclipse-leda/leda-distro/releases/tag/v0.1.0-M3

[AhmedElkazzaz]

Yes It working manually using kanto-cm create.
But I want to use OTA to update the container from the AWS cloud.
Do you have any full documentation how can I publish mqtt messages from AWS IOT core to create and update container in Eclipse Kanto ?

[AhmedElkazzaz]

The container factory is working with me ,so I can publish from AWS to create a container.

topic
command//webasto:mydevice:edge:containers/req//create

payload
{
"topic":"webasto/mydevice:edge:containers/things/live/messages/create",
"headers":{
"response-required":true,
"content-type":"application/json",
"correlation-id":"0216d7cc-a22b-4c15-a358-289e0863bf92"
},
"path":"/features/ContainerFactory/inbox/messages/create",
"value":{
"imageRef":"docker.io/library/hello-world:latest",
"start":true
}
}
this worked with me ,but when I follow this documentation to use the update manager and desired state
https://eclipse.dev/kanto/docs/references/update-manager/update-manager-api/

I receive the command in my pi ,but nothing is happening after that.

Here you can find my config files

ahmed@raspberrypi:~ $ sudo cat /etc/container-management/config.json
{
"update_agent": {
"enable": true,
"readTimeout": "30s",
"rebootRequired": false
},
"log": {
"logFile": "/var/log/container-management/container-management.log"
},
"connection": {
"broker": "tcp://localhost:1883",
"keepAlive": "20s",
"connectTimeout": "30s",
"disconnectTimeout": "250ms",
"subscribeTimeout": "15s",
"unsubscribeTimeout": "5s"
}
}
ahmed@raspberrypi:~ $ sudo cat /etc/kanto-update-manager/config.json
{
"log": {
"logFile": "/var/log/kanto-update-manager/update-manager.log",
"logLevel": "TRACE"
},
"connection": {
"broker": "tcp://localhost:1883",
"keepAlive": "20s",
"disconnectTimeout": "250ms",
"connectTimeout": "30s",
"acknowledgeTimeout": "15s",
"subscribeTimeout": "15s",
"unsubscribeTimeout": "5s"
},
"thingsEnabled": true,
"agents": {
"containers": {
"readTimeout": "60s",
"rebootRequired": false
}
},
"reportFeedbackInterval": "30s",
"domain": "containers",
"phaseTimeout": "15m",
"rebootAfter": "30s",
"rebootEnabled": false,
"currentStateDelay": "60s"
}
ahmed@raspberrypi:~ $