Where do I change which .IMG file docker points to, where is the setting for that?

Trying to restore my old docker containers after my flash drive fried.

settings => docker => advanced

 

The docker img isn't the issue though, it's the templates you've lost that reflect how you've mapped data to each container that's the issue.  They're on (were on) the flash drive.

 

If it were me, I'd start from scratch.  At least you got your appdata...

Beyond all that, while using the old .img will work, you will have a ton of trouble with updating the containers as the docker system expects the templates to be present on the flash drive for any of that to work (ie: you will get a lot of "Was this container created using this application errors")

 

Would suggest looking at CA backup to make scheduled backups of both your appdata and your flashdrive

 

Would suggest looking at CA backup to make scheduled backups of both your appdata and your flashdrive

 

Horse, stable door, bolted springs to mind, but good advice for the future nonetheless..

Horse, stable door, bolted springs to mind, but good advice for the future nonetheless..

Today just seems to be the day to beat that horse 

Without the templates, docker.img is pretty useless. *

 

And with the templates, docker.img is easily regenerated.

 

* Technically, I think you could use the old docker.img to manually do the docker run command from the command line by specifiying all the parameters for it yourself.

 

Just putting all the parameters into the Add Container form in the normal way will create the template and download and run the docker.

* Technically, I think you could use the old docker.img to manually do the docker run command from the command line by specifiying all the parameters for it yourself.

Certain things will not work.  No webUI will ever be present on the dropdowns, unable to edit the container after the fact, and updates will not work (even if the docker run command is identical to what dockerMan sets)  Basically in a nutshell the aggravation in restoring the .img without templates just isn't worth it.

Agreed.

* Technically, I think you could use the old docker.img to manually do the docker run command from the command line by specifiying all the parameters for it yourself.

Certain things will not work.  No webUI will ever be present on the dropdowns, unable to edit the container after the fact, and updates will not work (even if the docker run command is identical to what dockerMan sets)  Basically in a nutshell the aggravation in restoring the .img without templates just isn't worth it.

Yes, you would basically be stuck with working with it from the command line. Once you had a docker running you could access its webUI (if it had one) by going to the correct port. But the only thing you could do with it from the unRAID webUI would be to delete it.

* Technically, I think you could use the old docker.img to manually do the docker run command from the command line by specifiying all the parameters for it yourself.

Certain things will not work.  No webUI will ever be present on the dropdowns, unable to edit the container after the fact, and updates will not work (even if the docker run command is identical to what dockerMan sets)  Basically in a nutshell the aggravation in restoring the .img without templates just isn't worth it.

Yes, you would basically be stuck with working with it from the command line. Once you had a docker running you could access its webUI (if it had one) by going to the correct port. But the only thing you could do with it from the unRAID webUI would be to delete it.

lol  a bunch of posts debating a point where we all agree on the same thing....

I remember most of the templates I used, so that shouldn't be a problem.

Also like I said most of the persistence data is safe.

 

If all else I can see all the docker settings, such as port numbers, etc.