Stateless container

[kadza]

Hi,

I came across an issue that isn't directly related to this docker image, but as it's related to the topic of containerisation I'm posting it here.

My node-red container is stateless. I setup the homekit plugin and it worked fine until I updated the image. After the update, the devices present in the app aren't synchronised with the server.

After a quick research I noticed two things:
Logs before the update:
2022-02-15T21:16:53.226Z NRCHKB:ServiceUtils [garden light:08f97fb592e46698] onCharacteristicGet with status: 0, value: true, reachability is true with context undefined on connection 854ccad2-7679-4424-a53b-1dbf909c28c9
Logs after the update:
2022-02-15T21:20:42.163Z NRCHKB:ServiceUtils [entrance light:79e11c5148783c6b] onCharacteristicSet with status: 0, value: false, reachability is true with context undefined on connection undefined

The homekit plugin creates a directory /data/nrchkb/

Without digging deeper I'm guessing that the homekit plugin persists pieces of information that are essential for it to operate.
Have you ever considered the stateless scenario? Is is possible? Which pieces of information/directories are essential to make it operate correctly?