Kyrin

While it doesn't seem like it was just yesterday, I do remember when I first built my first pair of Unraid servers about 10 years ago... So much has changed, back then I couldn't even have imagined being where we are now, but looking back, I'm so thrilled with the progress and where things are headed. Here's to another 14 years!

Wow, thanks, I missed that error. Guess it could be possible that it's on its way out... it's one of my two original USBs from when I first started using UnRAID almost nine years ago...

So this is a weird one I've not encountered before, and I can't seem to draw a correlation between dockers that I can and can't edit... For background, I had an unclean shutdown last night, things started up just fine afterwards, including all my usual dockers were running and responding normally... Now, I don't normally make changes to my dockers as the system is pretty stable and as such I don't tend to change things, simply update the containers when there's an update. So, it's possible the issue may have been around a bit longer than just since last night, I can't be sure if the unclean shutdown was responsible for part of this or not. Core Problem: When I click to Edit a docker, the form comes up with a blank default form, not one containing all the information from my current docker... This is the case for several of my dockers (sonarr, SABnzbd, nzbget, Couchpotato), while I have many more that are showing up just fine (PlexMediaServer, plexpy, ombi, netdata), and this doesn't seem to matter if the docker is stopped, or running... I've attached the diagnostics from the server in hopes this will help. Cheers, G rewot-diagnostics-20181217-0923.zip

Which network do you need to assign the static on? For your primary network you can do that in the docker config page if you want it on its own IP (separate from the host) when you choose to bind it to 'bond0' or whichever your network is called, and on the secondary, 'iotnet' network, it's specified in the 'docker network connect' command... Shouldn't need to rely on DHCP for either if you don't want.

If you've already clicked on the 'Update Ready' bit, ensure that the toggle on the right is 'On' and then hit 'Apply' at the bottom of the page and it should "reinstall" all the packages and that would ensure the update gets applied.

After having just updated to 6.4.1 I hadn't updated my NerdPack, which was what led to missing the fact that there was this update, which has since fixed the issue... The 10 minutes of my life I could have had back from just updating everything first and then ssh in, rather than first ssh in, go crazy that it doesn't work, and fix that first... Edit: Also, it works fine with PuTTY, thanks dmacias, no need for more work!

You'd have to start the docker, and then manually connect it to the second network, and then give it say 5 minutes and check the XML response from /servers (https://192.168.1.100:32400/servers ) and see if it lists it there (dunno if it will or not), or just watch the Plex log files for it refreshing its network info... It may be of value to not have it see the gateway on that network, or at least not be able to get to the Internet via that network, so it won't try and register with the Plex mothership via that network... Damn... 12:44a here, I was supposed to be catching up my time tracking tonight, not upgrading to 6.4.1 and playing with new features...

At startup Plex will bind to all available IPs, the limitation is more with the single docker having the two NICs assigned and less the Plex Server application itself... Depending on the docker, you could potentially do this... It's well beyond the current scope of Docker on unRAID, but it looks like it can be done now... Here's some reading if you fancy yourself a Wizard: https://hicu.be/docker-networking-macvlan-vlan-configuration The key bits are about a quarter, and half way down... I can transpose them for what commands *MAY* work for your scenario... First you'll need to make a second macvlan: docker network create -d macvlan \ --subnet=10.10.10.0/24 --gateway=10.10.10.1 \ --subnet=2001:db8:babe:20::/64 --gateway=2001:db8:babe:20::1 \ -o parent=eth0.20 \ --ipv6 \ iotnet Then you would attach your plex docker to the second network docker network connect \ --ip=10.10.10.100 \ --ip6=2001:db8:babe:20::3 \ iotnet \ PlexMediaServer Now, this may, or may not work, even if the commands attach the docker to the networks properly, I don't know if Plex rereads the networking config when things change after it's started... That said, I've just tested this with my Netdata docker, and it works like a charm, and automatically detected the network change... *** All examples are provided without warranty or guarantees of fitness for use. Only a fool blindly copies and pastes from the Internet into a shell window. I am not responsible for your actions. ***

So, I totally have the same thing, but turns out it's when using screen, not when just SSH into the server... Screen version 4.04.00 (GNU) 19-Jun-16, installed via NerdPack plugin... after some digging I figured out it was the termcap, for some reason screen is starting and using the vt100 term, even with no changes made to PuTTY or anything else (other than upgrade to 6.4, still present in 6.4.1 btw), it's doing this now, despite TERM=xterm being present as a system variable prior to starting screen... The fix is simple, just add '-T xterm' to your screen start command (capital T is important), or add this alias to work around your habits: alias screen='/usr/bin/screen -T $TERM'

That's not a bad idea, might chat to the fellas about that, only problem is mitigating the risk for those running from command line on other operating systems, I can see issues with the ro being left off.... Any chance of getting this back, or is there another place I can pull the image from? I've been using it quite regularly prior to having to reload my main docker image, and would like to get it back on my system...

Heya, sorry to revive an old topic here, but I'm in a situation where I need to read my XFS disk and I've got Linux Reader installed, but the log is stating 'File system is not supported' when I try to mount it...

Now I don't know the process, but I'm just curious how to request the addition of a container, or if that's even a thing... but as upStatsBoard is somewhat dead, and I'm sure people are looking for an alternative, I was wondering if we could get a container for Plex-Board (https://github.com/scytherswings/Plex-Board) somehow... Though it's still in somewhat early active development, it looks like a good start and I think the exposure would help the project keep moving along EDIT: Okay, so I went and made one (my first docker ever btw gostlund/plex-board), and in actually using it, I realize it's still very early stages and not really something people would use in production yet... So, don't worry about this one yet...

Tried that, no dice. Did you set the username to admin and use the password? At this point, we need to see the log from deluge. I've tried putting admin and my password. I've tried putting just my password. Nothing worked which was why I just wound up configuring Blackhole instead. Do I lose any functionality with Blackhole over Deluge? Like am I not able to DL torrents from sites that only have magnet links? Hey, so I was frustrated as hell with this as well and think I found the key to what might have been blocking you... In the Deluge web-ui, go to Preferences->Daemon and check 'Allow Remote Connections' because otherwise it just listens on 127.0.0.1 and the passthrough from docker-proxy on 172.17.x.x can't connect to it... Hope that helps! Oh, and you'll need to add an entry to the 'auth' file in your /config for CP to use (couchpotato:YOURPASSHERE:10)... If only Sonarr could connect to the daemon rather than the web-ui...

You have to edit the settings.json file while Transmission isn't running. The container will copy a settings.json file to /config only if it's absent. Weird... I swear I tried that... Thanks, totally worked that time I tried it... /sheepishgrin

@gfjardim: I am hoping that there may be a way for the Transmission docker to stop overwriting parts of the settings.json file... or for there to be an environment variable to set the bind address... I need to have transmission operate from an alternative IP address, and though I edited the line in the json file, it resets and I'm losing my mind here... Thanks?

So, I seem to be having a similar issue, but in my case it looks like the plexWatch.pl script isn't getting run... There was no .log files being created, and no recreation of the .db file, but if I connect to the terminal and 'perl plexWatch.pl' it creates all the .log files expected, and the .db, and it all appears to be working... However the problem that exists is it doesn't keep running the .pl file regularly as it should, so the files never get updated, though I can tell it's talking to Plex at least since the index page shows the live details from my Plex server activity... Thoughts?

Thanks for all the comments and feedback! I admit that it seems I'm behind on the documentation and new systems here, it's come a long way, I've creeped the forums occasionally, but really changed nothing in my system in four years, which is also reflected in my forum activity being essentially non-existent (http://lime-technology.com/forum/index.php?action=profile;area=showposts;u=10434) in the interim. By the sounds of it, I can just upgrade to v6 (perhaps transfer my key to a new USB first, just because old), and point the Docker container to a location on what used to be my "OS" disk... I'm sorry if I came off sounding like an ignorant @$$, that wasn't my intent, just turns out there's been a lot more changes to catch up on, and in all my looking for what I thought I needed to know, I didn't clue in to how things actually work now. I'll hopefully be able to post an update (and [sOLVED]) to this in the next couple weeks once I've had a chance to tackle this. Cheers, Gavin

To most easily summarize why I'm running a full Slackware install, I would not be caught at the end of the world running any system live off a USB key... I can't have my performance affected by the slow read/write of a system running on a USB key... Not to mention, my Pro keys are circa early-2010 and though technology has improved somewhat, I don't want to even come close to the 50-100,000 read/write cycles before failure. Which could at the very least cause slowly degrading reliability or further loss of performance... I have no problem upgrading to v6, merged with an updated Slackware install, if that's what is necessary, just point me at the docs and I'll follow them, I'm comfortable with Linux, been using it for years, I don't worry about adding packages, or maintaining things by hand, though I do realize it's what's gotten me to this place... I don't fear using Docker containers for replacing some of these things, though unless the Plex one is updated regularly, I may stick with my PlexPass txz releases... I do appreciate the suggestions, and am open to upgrading to v6, but I stand firm against running my entire system off a well aged USB key with a limited lifespan that would be accelerated using it in a manner it was never designed to be.

So, I originally went and did the whole "Install full Slackware x64 and build for unRAID" back when I was running on 4.5 or something, and upgraded to 5.0b6a... I've added disks, and services, but now it's grown as much as it can... Aside from doing stupid things like upgrading my last five 1.5TB disks to 2TB disks... It would of course figure that the version I'm running is one revision just before >2TB support was added to unRAID, and now I'm asking for some help/advice because it's been four years since I've had to do any of the low level stuff and can't really remember all the important bits I went through before... I've got to get the support for larger disks, and I also need to keep my AirVideo/Plex/SAB/SickBeard/etc and such working... So, I'm wondering what the best method to go about this upgrade might be (should I simply try and upgrade to 5.0b7?), or if there's an updated guide I could follow that won't take me two days to get this back up and running without a full reinstall or putting my current array in danger... Thanks to any who can help guide me here.

Thanks much, I was getting a little concerned I couldn't find much on the wiki for these releases...

Done... They appear to show up properly now, and the array is started, now I just have to get used to the new way of doing permissions, after the chmod/chown script is done... Is there a thing in the wiki to clarify what setting I should use if I want RO for all, and RW for specific users?

So, I've installed 5b6a to my unRAID server in the process of moving it to a HDD install vs the flash key, and am getting the MBR: Unknown message on almost all but my two most recently added drives... I will mention that the three most recent drives were cleared with the new preclear script and 4k-aligned, but only the two most recent ones were added to the system after I upgraded to 4.7... I have saved the mbr debug info using the command specified in the other topic, if there's a way I can use that information to tell what I need to set the MBR flags using the command in the OP of this thread, please let me know...

I added two bits of information to the wiki that I found important, most importantly was the bit about the Kernel build option for IA32 support, which is necessary to run 32-bit binaries under 64-bit OS. All things appear to be working great, except for the problem of "MBR: Unknown" which I'll have to deal with later since I didn't feel like doing it at 1:30am...

Unless this is his work, I don't know that I'm seeing it... That article also doesn't talk about 64-bit, so I don't think that's it either...

So... I don't suppose there's a version of unRAID that works with 64-bit Slackware 13.37, eh? I dropped the updated md files from my 4.7 USBkey into the kernel and ran into build problems compiling md.c and when I did a diff, I saw that there was quite a bit more than just a few changes... I was checking out the wiki (the article is somewhat old, so I figured I'd try a newer version of Slackware) and I don't know that I'm ready to update to 5.x yet, but I could if necessary, or if there's another version of 64-bit Slackware I should use instead to get my unRAID4.7, I'd be happy to give that a shot... The important part is that I need to get this running on 64-bit...