Hello MT Forums,
We are very happy that the container support is now officially released, thank you for all the work.
One thing we have noticed though, is that whenever we upgrade ROS version, the container becomes inaccessible. For instance; we install a container on ROS 7.6, with two container mounts, and then proceed to install the latest 7.7 release (7.7rc3 atm) by uploading ROS and container npk (arm64) to the device. After reboot/upgrade the container is in the stopped state and wont start again, with no information in the logs (no errors when trying to start the container again).
Removing the container and adding it again enables logging and reveals that there are permission errors for our container mounts, they have become read-only. We have tried removing and adding the mounts again using /container/mounts, to no avail.
In a last ditch effort we have written a script for migrating the container mount data to a new mount, but this is quite cumbersome.
Are we doing anything wrong or is this intended behavior?