Kushan

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

8 Neutral

About Kushan

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I haven't posted this beyond reddit so far, but I'm currently working on a guide on everything to do with using compose on unraid, you can check it out here: https://unraid.kushan.fyi/ I'll make a dedicated thread on it when it's more complete but for anyone reading this topic, feel free to take a look.
  2. That's really good to know! I haven't had time to look into the above yet, but more info on this is certainly helpful. That's great to hear! Thank you. If you need any help or thoughts on the implementation, feel free to reach out!
  3. I see both sides to this. DockerMan is essentially just a UI on top of docker with some additions to make it a little more user friendly but ultimately it's going to run the same docker containers under the hood. It would be nice if DockerMan was a little less unRAID specific. One way of doing that would be for it to store its metadata as docker labels instead of whatever it's doing to store that XML data now - there's a feature request here for this exact suggestion. It would then give you the best of both worlds by allowing you to manage your containers using whatever
  4. Oh hey, it's a me! Yeah, this is something I was hoping was already being done under the hood, but alas the docker manager used by unRAID handles metadata its own way (If anyone can point me in the direction of how that metadata is stored and used, please let me know). The template system used by unRAID is great, it makes adding docker containers pretty straightforward and blings them up on the dashboard, with a nice icon or direct link to the container's WebUI. The only issue is that this system is somewhat proprietary and specific to unRAID. If you're using an image
  5. I know this is quite an old post, but I've had this same error myself and I couldn't find a solution after a lot of Googling. I also couldn't see a response in this thread which helped. I have found a solution though, so in case anyone else ends up down a rabbit hole, here's what I've discovered. Keep in mind I'm not sure if I'm taking a hammer to crack a nut. In `\nginx\site-confs\default` the server_name is set to '_' which gets passed through to swiftmailer, causing it to send '_' as part of the EHLO. Some SMTP servers will reject this as it's not a valid domain name. You can
  6. I just found this thread dealing with the same thing. I noticed that all 8 of my disks were spun up all the time. If I manually spun them down, they'd all spin back up a few seconds later. Checking the log I'd see something like this: Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdh Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdg Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdd Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sde Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdb Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdf Mar 22 14:28:21 Ja
  7. Oh fucksticks, you're absolutely right. I was reading that page wrong this whole time 🤦‍♂️
  8. Apologies, I didn't realise there was a response to this (I'm new on the forum and didn't have notifications on). The problem with ignoring it is that the warning pops up again but the ignored warning is still listed. Here's what I mean (See how radarr is listed in both sections): I think this happens when the container gets updated (Or recreated), but I haven't tested that theory much. I appreciate this is because I'm doing something that's not widely supported (Docker Compose), I'm happy that I won't get the templates or access to them, I'd just like to be able to reduce the n
  9. Sorry if there's a good answer for this. I did a search and seen a few people posting the same issue, but couldn't see any resolution. I have a bunch of missing template errors on my docker containers: When I click "apply Fix", I get an error: Now, I created these containers using Docker Compose as I had my compose file already defined from a previous NAS. I suspect that's the crux of the issue, so my question is: Is there a way to properly fix this, so the templates can be applied? (Ideally without having to do it ea
  10. Sorry to bump an older thread, but I'm getting this same issue with my containers. Now I think it's self inflicted as I'm creating my containers via docker-compose (old habits die hard and all that). Clicking the fix button gives the error in the screenshot above. I'm not actually bothered about the templates, but the warnings are a bit annoying. Is there a way to add these templates via compose or some other method? OR a way to turn this particular set of warnings off?
  11. I'd heard of unRAID from various places, but had been rocking a Synology NAS since about 2016. It suited my needs absolutely fine, but I had been pushing it more and more as of late. The final straw came when some docker containers stopped working due to the kernel being too old. I had thought about building a new NAS myself off and on over the years, but this felt like the right time. I looked into several solutions and settled on giving unRAID a go. The trial made it an easy choice. I built my new machine and fired up unRAID last night to play about with it. This
  12. Kushan

    RSS feed?

    I just came here because the main blog doesn't have an RSS feed I know they're a little bit old hat, but I've yet to find a better way of digesting a ton of different information sources. Social media has too much noise, email isn't any better (and is much harder to keep organised). I don't want to have to manually visit different sites just to see if there's more content, I want to pull that information in and sort it at my leisure.