I know I can manually add new paths, variables, etc in existing docker containers but determining the proper associated values isn’t really a simple process if you have many containers. Is there a process of deleting containers and re-installing that will pull new templates without losing existing settings?

The system updating the templates as it updated the containers was removed a couple of years ago as it proved to be more troublesome than it was worth.

 

I would open two tabs to the OS.  One on the docker tab, and from there edit each container.  In the other tab, open CA and within Settings enable Allow install second instance, then within Installed apps if you hit install second from Actions you can compare the two templates between the tabs and make appropriate adjustments.

 

Other than that, delete and reinstall (not reinstall from previous) is the way to go.  So long as the name of the container matches the appdata will still point to the correct location

2 minutes ago, Squid said:

Other than that, delete and reinstall (not reinstall from previous) is the way to go.  So long as the name of the container matches the appdata will still point to the correct location

I’ll just need to have screenshots of my configuration right?

Alternatively if you want to live on the. darkside you can also edit /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php with nano at the command line and around line 630 you will see

 

	public function updateUserTemplate($Container) {
		// Don't update templates, but leave code in place for future reference
		return;

 

delete the line that says "return;" and then force an update of each container.  Definitely this isn't tested though

 

2 minutes ago, wgstarks said:

I’ll just need to have screenshots of my configuration right?

yes

48 minutes ago, Squid said:

Alternatively if you want to live on the. darkside you can also edit /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php with nano at the command line and around line 630 you will see

 

	public function updateUserTemplate($Container) {
		// Don't update templates, but leave code in place for future reference
		return;

 

delete the line that says "return;" and then force an update of each container.  Definitely this isn't tested though

 

I try to avoid playing guinea pig.😁

You can also copy a backup of the .xml file for reference or to diff, just don't make a backup directory as there is a bug that will pull the file from that backup directory instead.