Edit: so this is what I've pieced together so far:

• Docker templates: /boot/config/plugins/dockerMan/templates-user/
• container order: /boot/config/plugins/dockerMan/userprefs.cfg
• containers currently in use/deployed: /var/local/emhttp/plugins/dynamix.docker.manager/docker.json (actually this is also shown by userprefs.cfg)
• auto-startup with startup delay: /var/lib/docker/unraid-autostart

 

 

Pre-edit post follows:

The docker templates are located in /boot/config/plugins/dockerMan/templates-user/ and container data in /mnt/cache/appdata/;
what about the current state of containers used, ie the composition - which containers are actually in use? This question asks something similar, but doesn't quite answer the question.

Grepping suggests this file reflects the current state of play: /var/local/emhttp/plugins/dynamix.docker.manager/docker.json

So is it a valid file to back up (and later use on recovered system)? Looks like the entire /var/local/emhttp/plugins/dynamix.docker.manager/ directory could be backed up, as it also contains the images/ directory.

 

Container order appears to be in /boot/config/plugins/dockerMan/userprefs.cfg

 

Where would the container startup delay be stored at though, as the files above define no container startup info we set in the UI.

Edited November 28, 20205 yr by laur

So I suppose following files/dirs should be backed up (someone please correct me if this looks wrong):

- /boot (you likely want to back /boot up in its entirety anyway)

- /var/lib/docker/unraid-autostart

- /var/local/emhttp/plugins/dynamix.docker.manager/docker.json actually no need for this - /boot/config/plugins/dockerMan/userprefs.cfg also reflects which containers are currently deployed; still docker.json explicitly defines which template is used for given container, so you might want to include it anyway.

Edited November 17, 20205 yr by laur