I am trying to understand how persistence is managed with App Services when using Docker Compose.
Here's my simple config:
version: "3.7" services: n8n: image: xxx.azurecr.io/n8nio/n8n:0.113.0 restart: always volumes: - n8n-data:/n8n/data volumes: n8n-data: driver: azure_file driver_opts: share_name: shareName storage_account_name: storageName
I've observed the following:
It boots up, and I can write to disk (sqlite).
Data survives a reboot and stop/start of my app.
If I go looking for my the contents of my share name, I do not see any data being written to it (where is the data being written?)
I've also tried the same config w/o any volumes defined, and I noticed that data does not survive reboots, which is what I would expect. I guess the strange thing I'm trying to figure out is...where is this data? Perhaps I don't need to explicitly say anything about azure_file and just mention volumes generally and it works? This is pretty underdocumented behavior so I wanted to understand what I can rely on and what I can't.
I'm using Basic B1 tier app service plan.