Jump to content

Trunkton

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Trunkton

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Trunkton

    DSM UI On docker + unraid

    I was pretty excited to give this a try depending how the thread was going. Owning a Synology the file manager and app UI is a first-class experience. Good news is this project is on github, and anyone can fork that and make modifications to improve upon it. I see one user has out of the few forks there.
  2. Trunkton

    [Plugin] CA Appdata Backup / Restore v2

    Squid! Thanks for an amazing app, I'm using it on all my new docker containers which sit outside of the array (but mounts encrypted with the array) and absolutely appreciate all the service and support you are doing.
  3. Trunkton

    Server Layout Plugin for unRAID v6

    Thanks for this plugin! I shut down my array, identified things and realized my soon to be parity drives are occupying bay 1 and 4 instead of 1 and 2 lol. Just a suggestion, if you were to put this repo on github I wonder if others would collaborate or fork to make their own improvements on this great app then merge them back in for a better experience?
  4. Trunkton

    Edit Sudoers List?

    THANKS!! I will look at switching out details in my /boot/config/go file to that right now, I didn't know it was out there very useful. UPDATE: That plugin does not do things pre-mount just after the array mounts or on a schedule from what I can see.
  5. Trunkton

    Edit Sudoers List?

    Thanks!!
  6. Trunkton

    Run dockers as non-root user, anyone try?

    Squid, you're everywhere! Thanks for the info appreciate it. I installed the SSH Plugin by docgyver and now my normal user can SSH in. It is not part of the sudoers list so I'm working on changing that then I'm thinking Dockers will get run with sudo command (effectively as root anyway) and I'll lock out root from SSH via GUI and take a backup first.
  7. Trunkton

    Generally pretty slow perfomance

    Hi Henning, Check this out, it sounds like the same issue that you're having: Am not poster here but I found it informative and ended up doing the same. To mitigate this issue on my end what I ended up doing was building the array with cache drive SSD then going new config and removing the SSD setting all options on all shares beforehand to use cache=no and run mover before going new config. Now, Docker and VM's run completely independent of the array to preserve performance. If/when I elect to use a cache drive it will be spinning rust not an SSD to only be used as a cache. Hope that helps!
  8. Good day! I was wondering if anyone's had any success with SSH enabling then granting sudo to their secondary users on unraid? I'd like to run my docker compose script which fires up a bunch of things to run without having the entire system running under roots credentials. unraid is so exciting! Why I'd like to do this is because I'd really prefer if the directories inside of /config didn't end up getting owned and grouped to root who shouldn't have to be running that side of the show at least thats my thoughts. Just today, I got a UPS dashboard notification that power went out, UPS was running on batts and then it came back 2-3m later (I found out 2h after the fact). Now, that is something I don't get rolling my own solution in Ubuntu Server (in addition to many other things).
  9. Hey BLKMGK, Thanks for commenting I see where you're coming from. Two reasons: -I get control of how that data is disseminated in case I choose to change it, something I do not get without encryption. Now I have the flexibility to put the password somewhere online, internal on the network or secondary USB called "Encryption Key" (Label maker n all). -When a drive gets pulled for RMA, recycled, gifted or resold, I sleep a lot better knowing things are not wide open searchable. I have a hell of a time with Dockers working on unRAID by having to manually do the unlock. The answer I suppose is prevent the Dockers from auto-start but then why am I trying to automate anything if I have to jump on the box to do everything after a power outage event for example (which do happen but the UPS is there to prevent the worst). If I'm away from the house, someone powers on the box I don't wanna have to spend 30 minutes with someone unfamiliar doing support to get content I may possibly want remote access to, back.
  10. I hate that I never tried this before wiping my array >_< Auto-mount works. I am gonna copy things back in, restore the symlink and try my containers out again. Only way this can all go sideways now is if after all that the docker containers attempt to boot before the array does or something which I didn't plan for.
  11. Trunkton

    Encryption and auto-start

    THANK YOU!!! I am adapting this to simply: # auto unlock array cp -f /boot/config/keyfile /root/keyfile I copied the mounted keyfile under /root out to /boot/config/keyfile and placed this as first thing in go script. Hope it works, rebooting now. My reasons for not having to use some other devices are simple, I still want encryption and automatic mounting without wrecking my docker containers on my encrypted and unassigned SSD and if I ever want, can just get a USB drive out and plug it into unraid as "Encryption key" or something if I need that level of safety. UPDATE: It worked!
  12. UPDATE: I rebooted and tried my key again, it works! I am not sure what happened, one attempt with my invalid key then it won't take the good key until you reboot. Just glad it works and I don't have to hold for support. Emailed to close the ticket.
  13. It will be Pro after the licensing issues get fixed, on trial at the moment.
  14. It had been moved to the unassigned SSD which I had to wipe, there were no copies left unfortunately.
  15. Docker.img and the VM files first seeded to the array were moved manually to unassigned SSD (instead of copied) which meant even with my wiped array I couldn't use Docker because that file wasn't present in the array or SSD any longer. I googled for the file to see if there was mention of it on the forums here with nothing, only way that I know to get it back is to redo things from scratch. I power the system down, wipe the USB, redo it and get an error from the keyfile that my GUID isn't recognized anymore. I'm not sure if wiping it changed it or what but I will say this. I attempted to activate with the wrong key at first, but tried my current one (which I forgot I had) and same problem with activation. Now the license issue is in the hands of support for further action which I trust will be resolved it just sucks I have to wait it out now.