hios

No need to apologize. I'm laughing too. I know we've all been there many times.

I'm the idiot. Every. Single. Time. The array wasn't stopping due to something with /mnt/user preventing it so I just rebooted and the containers are gone. Someone should really tell every single person that interacts with technology that the first step of troubleshooting is to reboot the device. How is this not common knowledge?! /s. Thanks for reminding me of the basics.

I recently worked with a docker container that required command line interaction (fitbit-fetch-data). I had to run the container multiple times from the CLI. I used docker container rm/rmi to remove the containers and images, but I still see several containers showing up on the auto-update settings page. They don't appear on the Docker tab and they don't appear when I run docker ps -a. How can I remove these from the auto-update settings page?

Generating a new Mullvad config fixed it. No clue why the old one stopped working all of a sudden.

My container started throwing DNS failures last night out of nowhere. It's been running for the last year+ with no problems. I did restart the server twice during that time while trying to fix an encrypted volume that wouldn't unmount, but it wasn't in any way related to deluge. What's odd is that my binhex-sabnzbdvpn container is working just fine, with the same config. All other containers and Unraid are working just fine. I've tried: Stopping/restarting the container multiple times Restarting the server Changing the DNS servers back to the default (I was using Mullvad's, and am still using Mullvad's for sabnzbd) I could easily be wrong, but based on the logs it seems like the vpn starts up and gets a public IP. However, I can't ping from the container and a website port checker says the connection isn't open. My logs are attached and I'd appreciate any thoughts, as I've spent a few hours on this today and didn't get anywhere. supervisord.log

Thank you! That worked. I figured it was something simple I was missing. For anyone with noob issues like me, here are the steps: Go into the veracrypt-gui console and create a new sub-directory under /mnt/disks, so it would be /mnt/disks/subdirectory. Not sure if it's needed, but I restarted the container. Open the veracrypt gui. After selecting the encrypted volume you want to mount and clicking the "Mount" button, click the "Options" button in the lower right of the dialog. At the bottom of the expanded dialog you'll find the option "Mount at directory." Click the "Select" button and select the new sub-directory you created. Now you can mount the volume and it should be available outside the container.

@primeval_god, @engardeknave Sorry to resurrect an old thread, but I can't figure out how to mount a veracrypt volume to a subdirectory of /mnt/disks in the container and I feel like an idiot. I can mount a veracrypt volume inside the container with no problem but, although I've specified the docker volume mount as "Read-Write - Shared," I can't see it outside the container. Where/how do I specify a subdirectory of /mnt/disks? In the docker config or in the veracrypt GUI? If it's in the GUI, then I'm completely failing to see how to do that.