A close to real-life showcase for truck fleet management where trucks run an SDV software stack so that logistics fleet operators can manage apps, data and services for a diverse set of vehicles.
The Leda deployment guide describes in detail how to set up the in-vehicle containers in Leda.
However, the FMS Forwarder component fails to start on Leda after the fms-forwarder.json manifest file has been created.
The /var/log/container-management/container-management.log file contains the following:
time="2023-08-21T07:47:21.788489091Z" level=warning msg="[container-management][ctrd_client_internal.go:44][pkg:github][func:com/eclipse-kanto/container-management/containerm/ctr] the d
efault resolver by containerd will be used for image ghcr.io/eclipse-sdv-blueprints/fleet-management/fms-forwarder:main"
time="2023-08-21T07:47:22.261538778Z" level=info msg="trying next host" error="failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized" host=ghcr.io
time="2023-08-21T07:47:22.295893405Z" level=error msg="[container-management][ctrd_client.go:94][pkg:github][func:com/eclipse-kanto/container-management/containerm/ctr] error while tryi
ng to get container image with ID = ghcr.io/eclipse-sdv-blueprints/fleet-management/fms-forwarder:main for container ID = fms-forwarder \n\t Error: failed to resolve reference \"ghcr.io
/eclipse-sdv-blueprints/fleet-management/fms-forwarder:main\": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized "
which seems to indicate that the container image cannot be pulled anonymously from GHCR.
The Leda deployment guide describes in detail how to set up the in-vehicle containers in Leda. However, the FMS Forwarder component fails to start on Leda after the
fms-forwarder.jsonmanifest file has been created.The
/var/log/container-management/container-management.logfile contains the following:which seems to indicate that the container image cannot be pulled anonymously from GHCR.