4/7/2023 7:02 AM | |
Joined: 4/7/2023 Last visit: 8/21/2024 Posts: 3 Rating: (0) |
Hi All, I read about the example image that I can build from the meta-iot2050 repository and the industrial OS that I can download ready to be flashed on device. My questions are:
From my point of view the best way is to extend meta-iot2050 with a new layer, but the only document that I find for now is this but I don't think that customize an example image is a stable production solution. I am not able to find how to add a new image and integrate it with the kas-container script. Best regards, Stefano. |
4/10/2023 7:36 PM | |
Joined: 10/22/2020 Last visit: 10/1/2024 Posts: 169 Rating: (6) |
Hello Stefano, The main differences between the IOT2050's example image and the IndustrialOS are:
In terms of customising the example image and adding or removing software, we recommend that you create a new layer that inherits the base layer, as in the linked explanation from your last post. This approach allows you to maintain a clean separation between your customisations and our base layer, making it easier to manage and maintain your production image in the long run. In your new layer, you can add or remove software by changing the package selection and configurations. To remove Node-RED, as you requested, you can use the following in your layer's conf file:
To disable a service with systemctl on a running (example) image, you can use the following command:
These commands will prevent the services from starting automatically during the system boot. From this point on, the image can be adapted and extended directly on the IOT2050 as you need it. One solution could be to set up an IOT2050 completely by yourself and distribute the SD card image to other IOT2050s from now on. However, we do not recommend this procedure, as it is absolutely unsustainable. BR |
Last edited by: apastore at: 04/10/2023 19:37:11Last edited by: apastore at: 04/10/2023 19:38:10 |
|
This contribution was helpful to2 thankful Users |
Follow us on