I have created an update lock on
/data/resin-updates.lock in a container, however the device containers were still updated when I pushed to balenaCloud.
I fear that the update lock is not recognised, perhaps this is due to working in a multi container environment. Or could this be due to the named volume being called
resin-data where in the updated instructions the volume is called
Here is the relevant portion of the
docker-compose.yml in which the volume is created.
version: '2' volumes: resin-data: services: controller: volumes: - 'resin-data:/data'