Squid

Community Developer
  • Posts

    28636
  • Joined

  • Last visited

  • Days Won

    314

Squid last won the day on March 3

Squid had the most liked content!

Retained

  • Member Title
    What would Chode do?

Converted

  • Gender
    Male
  • Personal Text
    AKA Flesh Gordon

Recent Profile Visitors

71677 profile views

Squid's Achievements

Grand Master

Grand Master (14/14)

  • Great Support Rare

Recent Badges

5k

Reputation

283

Community Answers

  1. How are you editing? Docker containers' appdata files have their own unique ownership and permissions which may or may not be compatible with editing via SMB. You could always edit at the command prompt, or Dynamix File Manager
  2. Reason for not available would be that it failed to be able to check the current versions from GitHub. Try setting static DNS addresses in Network Settings, DNS Servers. #1: 208.67.222.222 and #2: 208.67.220.220 and see if that makes a difference.
  3. Can you install Fix Common Problems via the Apps tab and run it. I *think* you may have inadvertently sent stuff to /mnt/disk3 or something that doesn't actually exist. FCP should show that.
  4. "swingmusic": { "Blacklist": true, "ModeratorComment": "Repository does not exist on docker hub
  5. Did that "! Not valid!" actually show up in the popup within CA?
  6. There seems to be some confusion etc as to what this plugin is actually doing. As I've said, it's not fixing a bug with the OS. Nor is it patching docker itself (and undoing the security updates which they did). In pseudo code, pre 6.12.8 Unraid handled installs and updates to containers like this 1. Loop through all of the paths listed in the user's template 2. Add the appropriate flags / path to the docker run command 3. End loop Because of how many users set up their templates, the above would generate an error if the host path (or container path) was empty on 6.12.8. The revised code is this: 1. Loop through all of the paths listed in the user's template 2. If either the host path or container path is empty, then skip this path 3. Add the appropriate flags / path to the docker run command 4. End loop Actual code snip I'm adding in (and is included in future revs of the OS) is the second and third line of the following: if ($confType == "path") { if ( ! trim($hostConfig) || ! trim($containerConfig) ) continue; $Volumes[] = escapeshellarg($hostConfig).':'.escapeshellarg($containerConfig).':'.escapeshellarg($Mode); This plugin has to remain installed while you're on 6.12.8. Installing it and uninstalling it (with a reboot) will undo the changes it's adding in. Once you upgrade the OS to a later version, the plugin will automatically uninstall itself - IE: there's no need to uninstall it when you upgrade - the system won't even give you the option since it won't even get installed during boot of the next releases of the OS.
  7. On the docker tab, switch to advanced view. Then down at the bottom of the list you'll likely see a whack of orphaned containers. Click on each of the icons and say Remove
  8. Not seeing this issue. What OS version are you running? This is from 6.12.8
  9. Can you post your diagnostics. Also, if you delete the .DS_Store file rm "/mnt/user/Personal and Backups/Backups/.DS_Store" and then disconnect and reconnect the server / folder in finder does it show correctly?
  10. I would install the updates for your BIOS and see if that makes a difference. You're several versions behind https://www.msi.com/Motherboard/B350-TOMAHAWK/support Release Date: 01/23/2019
  11. Yeah, everything you were showing implies a flash drive problem. I'm surprised though that a banner wasn't displayed across every page stating Flash Drive corrupt or offline.
  12. It's a catch-all notification. To separate them into individuals, you'd potentially get multiple notifications simultaneously. Once you see the notification, if you're comfortable with ignoring it, then hit Ignore and FCP won't send a notification if that's the only thing found. FWIW, I classify them as warnings or errors, and you have have it not send notifications for anything, or only for errors, or for everything
  13. It's not the contents of your flash drive. That is /boot. Likely you've set the backup plugin to use /mnt/user/flash as a destination
  14. There's more than one person who looks at stuff here to help users, and contrary to popular belief there are other things I do in life I would look at the settings for the proxy editor, or ask wherever the support is for that plugin. The problem started immediately after updating the plugin
  15. Basically, in order to determine (without being the owner of the container itself), you have to pull it to be able to grab the date of it. IE: Catch 22. To determine whether its X days old and then update what you've got installed, you have to update what you have installed.