/var/crashplan/conf/my.service.xml does not persist over time and remote connections fail

[cerealsoup]

The <serviceHost> tag in /Container/crashplan/conf/my.service.xml reverts from "0.0.0.0" to "localhost" after a restart.

If I ever need to use the GUI I have to:

1. stop the container
2. edit my.service.xml tag to <serviceHost>0.0.0.0</serviceHost>
3. Start the container.
4. Pull the .ui_info information, copy that locally (because it also gets regenerated)
5. Then finally can access the GUI.

Where would my.service.xml be getting the "localhost" value from?

The last comment here was a huge help for me after months of poking around in this in my spare time. I also adopted this backup from a non-headless configuration from the past. Now if I could only get it to persist...

This is the command I used to get the ball rolling (Crashplan works well and is backing up regardless of this issue of being able to access the GUI) docker run -d --name crashplan -e America/Los_Angeles --net=host --volume /share/CACHEDEV1_DATA/Container/crashplan/config:/var/crashplan --volume /share/CACHEDEV1_DATA/Backup:/storage jrcs/crashplan:latest (without line breaks)

...which I changed from the below as a results of my first attempt to try and resolve this. I provide this just in case it's useful but the above is the current setup...

docker run -d --name crashplan -e America/Los_Angeles --publish 4242:4242 --publish 4243:4243 --net host --volume /share/CACHEDEV1_DATA/Containers/crashplan/config:/var/crashplan --volume /share/CACHEDEV1_DATA/Backup:/storage jrcs/crashplan:latest (Note 's' on Containers)

Thanks for any support.