| Re: [leda-dev] Launching KUKSA:mock_service in Leda |
|
Hi, I would like to note it out here that the mock_service does work in Eclipse Velocitas, through custom created docker image.
From: leda-dev <leda-dev-bounces@xxxxxxxxxxx>
On Behalf Of Ivanov Vasil (BD/PAD-COD1) via leda-dev Someone beat me to it
🙂 From: leda-dev <leda-dev-bounces@xxxxxxxxxxx> on behalf of Ivanov Vasil (BD/PAD-COD1) via leda-dev <leda-dev@xxxxxxxxxxx> Adding to this, It seems there is an issue with the ":latest" mock service container, since it can't find its entrypoint (mock_service). I suppose this is due to the following reorganization
commit: But the kuksa team has forgotten to update the dockerfile:
https://github.com/eclipse/kuksa.val.services/blob/main/mock_service/Dockerfile I'll take care to open an issue in the Kuksa.Val repo. From: Heissenberger Christian (ETAS-E2E/XPC-Fe) <christian.heissenberger@xxxxxxxxxxxx> Hi, you do not need to have a “mock.py” on the Leda Image. It is just a possibility to modify directly the “mocks” without rebuilding and re-deploying the Container. You will see this, if you do leave the mount point empty:
"mount_points":
[], And open the logs of the mockservice container. E.g. with kantui
https://eclipse-leda.github.io/leda/docs/general-usage/utilities/kantui/
Christian Heissenberger
From: leda-dev <leda-dev-bounces@xxxxxxxxxxx>
On Behalf Of Antara Dey via leda-dev Hi, I see that the Leda documentation has been updated w.r.t the mock_service. However, I do not understand the purpose of mount_points in the container manifest. As adopted from Kuksa VAL, the mock.py is part of the mock_service app, and
mockservice.py executes in the container. Do I need to copy the mock.py file to the Leda image? If yes, why? Thank you for your support. Regards, Antara Dey From: Ivanov Vasil (BD/PAD-COD1) <Vasil.Ivanov3@xxxxxxxxx>
Hey, We were having some issues with releasing v0.1.0-M3 version of Leda, and I had to switch my focus to that. Now that is done and I can go back to looking into your
issue. Sorry for the delay. Best, Vasil From: Antara Dey <Antara.Dey@xxxxxxxxxxxxxxxxxx> Hello Vasil, Doing a follow-up on the mock_service container image testing.
Is there any update on this yet? Regards, Antara Dey From: Antara Dey <Antara.Dey@xxxxxxxxxxxxxxxxxx>
Hi Vasil, I have made the container image public for you to test. You can pull the image from here: docker pull
ghcr.io/antaradey-itk/mock_service:v0.0.1 Regards, Antara From: Ivanov Vasil (BD/PAD-COD1) <Vasil.Ivanov3@xxxxxxxxx> That is a bit strange indeed. Is it okay for you to make your container image public, so I can try to reproduce the issue on my side and more quickly iterate when
debugging? From: Antara Dey <Antara.Dey@xxxxxxxxxxxxxxxxxx> Hi Vasil, Thank you for writing back. Approach 1: As suggested, I switched the network to bridge, and added the extra_hosts for mosquitto and databroker. Even then, I see that the error persists. Approach 2: When you say I need to the map the mosquitto and data_broker to 127.0.0.1, could you please elaborate how to do that? Best Regards, Antara Dey From: Ivanov Vasil (BD/PAD-COD1) <Vasil.Ivanov3@xxxxxxxxx> Hi Antara, From what I see in your container descriptor, you set the environment variables as so: "env": [ "SDV_MQTT_ADDRESS=mqtt://mosquitto:1883", "SDV_VEHICLEDATABROKER_ADDRESS=grpc://databroker:55555", "SDV_MIDDLEWARE_TYPE=native", "RUST_LOG=info", "vehicle_data_broker=info" ] However, "mosquitto" and "databroker" don't mean anything to the kanto container manager and that is why you are probably getting RPC (connection) errors. If you want to use mosquitto and databroker to refer to the MQTT broker (native) on Leda and the databroker container, you would need to add some extra host entries: "extra_hosts": [ "mosquitto:host_ip", "databroker:container_databroker-host" ] Now, host_ip and container_databroker-host are special variables in Kanto manifests which resolve to the Host ip and the ip of the container with the name databroker
in the virtual bridge network respectively. Adding the above-mentioned extra host entries now map "mosquitto" and "databroker" to those IPs and this will allow your mock service to connect to both services (if everything else is ok). P.S. You can use the seatadjuster container as an example here:
https://github.com/eclipse-leda/meta-leda/blob/main/meta-leda-components/recipes-sdv/eclipse-leda/kanto-containers/example/seatadjuster-app.json.disabled#L17 P.S.2: If you do the extra hosts re-mapping the way I suggested, you shouldn't need in host networking mode. If you still decide to run in host-networking mode, then
you would need to map both "mosquitto" and "databroker" to 127.0.0.1. P.S.3: In docker, on the default docker0 bridge network you don't have a DNS server that allows container-name based communication and I assume that's why you can't get
it to work without host networking. Overall, I suggest going with the approach I described in the beginning of this email and if you need further help, don't hesitate to write back. Best regards, Vasil From: leda-dev <leda-dev-bounces@xxxxxxxxxxx> on behalf of Antara Dey via leda-dev <leda-dev@xxxxxxxxxxx> Hello Leda community, I am trying to launch the mock_service from KUKSA as Kanto container in Leda image. Steps: 1. Import
mock_service from KUKSA repository into Velocitas template. 2. Modify vehicle signals for vehicle application and test it. 3. Create docker image, and push to private repository. 4. Pull docker image and run in Velocitas environment. ->
Runs as expected. 5.
Use Kanto-CM container manifest to launch in Leda v.M2 image. 6. Restart Kanto-CM. The creation of the mock_service container is successful. But, it throws the following
errors
in logs and
does not run as expected.
As suggested by Velocitas team, I have referred the Velocitas Kanto manifest file for mock_service from
mockservice.json. Please find attached JSON file of the mock_service which I use in Leda image. Note: I observe the
same error in Velocitas in the following scenarios: 1) Container launched without Local-Runtime Up. 2) *docker run* without flag --net=host. Kindly provide insights into this issue. Kind regards, Antara |
