Plans to update docker image?

[Bubblesaway]

@ts678

I have asked at the above workaround link to find minimal steps. Alternatively, you could help find.
You would need to be able to run the image without TrueCharts. Anybody else here willing to test?

After having found what we think is Dockerfile fix, it would be good if a pre-Canary test is possible.
I’m not sure if Docker build is in the preview linked above. If so, that suggests this path is possible.

I think minimal steps can be found in this post: Http send report errors / duplicati-monitoring - #16 by hairlesshobo

@hairlesshobo

##!!! use at your own risk.. I do NOT suggest deleting the offending cert 
##!!! but instead moving it to another location in case you need to put 
##!!! things back the way they were for some reason.

# update apt
apt-get update

# make sure the latest ca certs are installed
apt-get install ca-certificates

# remove the offending root cert from the root store
mv /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt ~/DST_Root_CA_X3.crt 

# update the root ca store.. this automatically updated mono for me.
update-ca-certificates

But it might also be the case that moving to a different base OS might fix the issue, since the root problem is “old” certificates.

It might also be the case that this isn’t even a problem on Canary builds, be it by a change to Duplicati’s code (doubtful) or by just an update to the image (my theory is it does work). Again, something I can test (once I figure out how access the Duplicati interface after running the container).