🇨🇦Samuel Proulx🇨🇦<p><span>A deeply annoying discovery I made today: if you have an </span><a href="https://fed.interfree.ca/tags/rclone" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#rclone</a><span> mount that needs to be restarted, any running </span><a href="https://fed.interfree.ca/tags/docker" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#docker</a><span> writing to that mount is now writing to your filesystem without warning. I get that if the mount is gone, of course it has to write to the local filesystem. But when the mount comes back, it continues writing to the local filesystem, but if you change into the mounted directory, ls will show the contents of the mount, not the contents of the local filesystem that docker is busy writing to, and you will have no idea what black hole your files are falling into, because /mnt/offsite shows it's mounted, your docker agrees that it's writing to /mnt/offsite, and yet the files are nowhere to be found when you go to /mnt/offsite! They only suddenly appear when you umount the directory.</span></p>