I've made progress getting a process in place that can convert a Beaglebone image to an ostree-managed version of it. When the ostree-managed system is running, the root directory (/) is actually a bind mount to a path buried in the ostree repository (something like /ostree/boot.1/debian/72448a25b05b4af57ed48c72bea09e50643b90bfaad5125bfd022a6aa67aac2c/0). /var is a better place to write to as it remains a mutable location to store files. In this pull request, I switched tools/grow_partition.sh and boot/generic-startup.sh to write to /var rather than /.
I've made progress getting a process in place that can convert a Beaglebone image to an ostree-managed version of it. When the ostree-managed system is running, the root directory (/) is actually a bind mount to a path buried in the ostree repository (something like /ostree/boot.1/debian/72448a25b05b4af57ed48c72bea09e50643b90bfaad5125bfd022a6aa67aac2c/0). /var is a better place to write to as it remains a mutable location to store files. In this pull request, I switched tools/grow_partition.sh and boot/generic-startup.sh to write to /var rather than /.
See https://github.com/ostreedev/ostree/issues/2357 for more info about the ostree conversion.