Slartybart
Slartybart
OK. My bad... was using wrong password. Have logged in and now faced with this: 
Thanks.... I think the second issue was even more simple, that the drives had lost their mapping details. I've re-linked them using the 'Volumes' settings in the Synology Docker container...
Ha! To be honest, I've no idea, but probably not..... it's such a long time since I had to do anything other than update the container, largely thanks to your...
Is there a way to map other external drives, as most of my Crashplan files are on drives other than the Volume 1 internal disks? Thank in advance for any...
PS... Sorry if this isn't a bug, they seem to have changed the way of reporting issues.
I assumed it was a newer version of Docker, but I may have got it confused with the new ‘container Manager’. It seems to be 20.10.23-1413. It’s on a synology...

Sorry for the delay... is this what you need? 
This is with my Synology: I ended up deleting the container and starting again. When making the new container I assigned 'high privileges' to the new container, set the ports...