September-21st-2018, 08:33 AM
Thank you Paul.
I am glad to hear that you can recover your system.
But still I am very curious guy and I want to understand the root cause of the problem and maybe I can get your problem reconstructed.
So basically when you clone a running container, by tagging it, my expectation is that Docker Deamon makes a 1:1 copy. And afterwards when you start your copy everything should work as before.
But let me ask you this: have you stopped the Node-RED container before cloning it? Maybe that is the problem. A container you make a copy from should never run, cause there are threads running that maybe use cached data in RAM. So in this case a flow file could easily not being placed on the SD card (deleting the file first was executed, but not writing) and then a copy of course will also not include this file.
Thx
Armin
I am glad to hear that you can recover your system.
But still I am very curious guy and I want to understand the root cause of the problem and maybe I can get your problem reconstructed.
So basically when you clone a running container, by tagging it, my expectation is that Docker Deamon makes a 1:1 copy. And afterwards when you start your copy everything should work as before.
But let me ask you this: have you stopped the Node-RED container before cloning it? Maybe that is the problem. A container you make a copy from should never run, cause there are threads running that maybe use cached data in RAM. So in this case a flow file could easily not being placed on the SD card (deleting the file first was executed, but not writing) and then a copy of course will also not include this file.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)