Since it's always changing, it gets flagged for backup every night by Crashplan. At this rate, at 20 GB a night, I'm going to have over 600GB in versions of the same file in a month's time. It also extends my backup time by some margin.

 

Does this even need to be backed up? We all already know that settings, configs, and other data for dockers are in appdata, and from what I can tell, templates for previously installed dockers are stored on flash. I'm already backing up both of these locations, so really if I were to lose my cache drive, I could theoretically rebuild all of my dockers from those templates and appdata really easily.

 

That being said, is there any reason at all why I should be backing up the image?

Edited July 11, 20178 yr by Phastor

1 hour ago, Phastor said:

is there any reason at all why I should be backing up the image?

No.

8 minutes ago, jonathanm said:

No.

 

Straight and to the point. Thanks!

 

Can the same be said for the libvirt image and pretty much the system share as a whole?

Edited July 11, 20178 yr by Phastor

The whole idea of Dockers is that they contain functioning code and no configuration data.

 

With the docker templates stored on your flash, you can rebuild them very fast. I recently recreated my docker on a fresh SSD. Took about 10 minutes.

 

I'd focus your backups on your irretrievable data. I'd probably including the "appdata" share on the cache, at least for some Dockers. If you have VMs (domains share), you might want to periodically back them up as well. But they can be big and it really depends on how much time it would take you to reconstruct. Even with VMs, you should be externalizing your data onto the array so backing them up may very well not be necessary, at least not very often.

14 minutes ago, Phastor said:

Can the same be said for the libvirt image

 

No, the libvirt.img stores all the VM XMLs.

Quote

I'd focus your backups on your irretrievable data. I'd probably including the "appdata" share on the cache

 

Yup! This is what I was thinking. I've got appdata and my flash already backed up on a nightly schedule. I'll remove the docker image from backup then.

 

As far as VMs, I don't have any yet. I'll probably spin up an ARK and Minecraft server sometime down the road. I might not map their data to an unRAID share directly, but I do plan for them to back up their world files on a regular basis somewhere to a share, which will then get picked up by Crashplan. I wouldn't backup the VMs themselves then since it shouldn't be too difficult to spin up new ones and restore their data.

how does backup store docker container settings? I lost unraid 3 times now and have to fill inn correctly every time. Have to remember every settings. 

how does backup store docker container settings? I lost unraid 3 times now and have to fill inn correctly every time. Have to remember every settings. 

Often it is recommended that the docker.img file be deleted and recreated to solve docker related issues; however, even if a docker container is simply removed without deleting the docker.img file, any and all previously installed docker containers can be reinstalled with ALL prior settings intact through the Previous Apps section in Community Applications (Apps tab in the GUI)

 

 

Sent from my iPhone using Tapatalk

wow, have to check it out. Thank you so much

On 4/26/2020 at 9:42 PM, Hoopster said:

...any and all previously installed docker containers can be reinstalled with ALL prior settings intact through the Previous Apps section in Community Applications (Apps tab in the GUI)

Thank you! I've managed to corrupt my docker image a couple of times. This is going to be a life saver.

On 7/11/2017 at 9:59 PM, JonathanM said:

No.

I setup a sharelatex container.

I install texlive-full by attach to the console of the container.

Then I commit the container and revise the docker template to use the local image.

Is the local image stored in docker.img?

If I do not backup docker.img, will I be able to have the texlive-full local docker image?

On 4/26/2020 at 9:42 PM, Hoopster said:

Often it is recommended that the docker.img file be deleted and recreated to solve docker related issues; however, even if a docker container is simply removed without deleting the docker.img file, any and all previously installed docker containers can be reinstalled with ALL prior settings intact through the Previous Apps section in Community Applications (Apps tab in the GUI)

 

 

Sent from my iPhone using Tapatalk

Is there any way of finding out which previous dockers you actually had active as Previous Apps includes anything you have ever installed.

3 hours ago, cinereus said:

Is there any way of finding out which previous dockers you actually had active as Previous Apps includes anything you have ever installed.

Not that I know of.   The dates on some of the xml templates might give a queue.    Another possibility is look at the folders you have under the ‘appdata’ share and look at their dates to see when they were last updated.

 

Probably a good idea to periodically tidy up the previous apps section removing any that you no longer use.

6 hours ago, cinereus said:

Is there any way of finding out which previous dockers you actually had active as Previous Apps includes anything you have ever installed.

 

Start by pruning any docker template XML files for dockers you no longer have installed.

 

You can do this deleting them directly from the USB, or, you can go through the GUI. Go to the docker tab, click "add container" at the bottom, then on the blank templating page, select a template from the drop-down menu, and click the little [X] icon to remove that template.

 

To easily restore all your docker containers after a docker.img wipe, you just go down the list of templates until you've got them all reinstalled.

Edited March 31, 20251 yr by MowMdown