== 1. install from TODAY's template
  container: healthy /srv/b2/userdata/media/torrents->/downloads /var/lib/docker/volumes/b2qbt_qbittorrent_config/_data->/config 
   default save path: /downloads
{"added_torrent_ids":["a5801fa9a8beb3f047303e352844db8898570758"],"failure_count":0,"pending_count":0,"success_count":1}
   torrent b2-old state= stalledUP progress= 1 save_path= /downloads
== 2. update to the NEW template (same volume)
  container: healthy /srv/b2/userdata/media/torrents->/srv/b2/userdata/media/torrents /srv/b2/userdata/media/torrents->/downloads /var/lib/docker/volumes/b2qbt_qbittorrent_config/_data->/config 
   entrypoint said: [felhom] default save path moved from /downloads to /srv/b2/userdata/media/torrents 
   default save path now: /srv/b2/userdata/media/torrents | temp: /srv/b2/userdata/media/torrents/.temp
   the OLD torrent after the update:
   torrent b2-old state= stalledUP progress= 1 save_path= /downloads
{"added_torrent_ids":["496bc2c1261736321d710aeca0e4c7c88a8bf946"],"failure_count":0,"pending_count":0,"success_count":1}
   a NEW torrent (no save path given):
   torrent b2-new state= stalledUP progress= 1 save_path= /srv/b2/userdata/media/torrents
== 3. B-3 from inside the container
   ls of the media folder path:
     torrents
   ls of the photos folder:
     ls: /srv/b2/userdata/media/photos: No such file or directory
   write into the photos path:
     rc=0
   on the BOX, the photos folder after that: family.jpg 
   and the container's own copy of that path is on: overlay
== 4. a FRESH install of the new template
  container: healthy /srv/b2/userdata/media/torrents->/srv/b2/userdata/media/torrents /srv/b2/userdata/media/torrents->/downloads /var/lib/docker/volumes/b2qbt_qbittorrent_config/_data->/config 
   default save path: /srv/b2/userdata/media/torrents | temp: /srv/b2/userdata/media/torrents/.temp
== cleaned up: 0 container(s), 0 volume(s)
