ZataH

https://www.plop.at/en/plopkexec/download.html This one, also linked it earlier in the conversation

Sorry I missed that. So from what I can gather, your VM can boot the VMDK, but it cant read the content in the boot process. I have never tried to boot this way, I have always used usb flash and plopkexec. That has always worked. Only flaw in that setup, is that you cant vmotion that vm.

If you get a "bond0" error. That should be network related. Try to login to your console. Do a "ifconfig -a" and after that edit your /boot/config/network.cfg and see if the interface match your output from ifconfig. Maybe your interface name has changed. Should be something like ethXX where is X is usually 0 or 1

I also use this, works great https://www.plop.at/en/plopkexec/download.html

Any news on update for 6.4?

When will it be updated for 6.4?

Why not? If the container are running on a different IP, this should not be a issue

I forgot to mention, I am running letsencrypt with fixed IP

After upgrading to 6.4, I have had some problems with my container that wont start. Tried to remove everything except my nginx config file yesterday, and now I am getting this error when trying to start letsencrypt: EDIT: I am running letsencrypt with fixed IP

Any ETA when this will work for Supermicro? I am not able to use fan control. Have this board: X10SRA-F

Why not just copy the files?

You can set some things from the gui, but some things are defined in you config file, and will therefor be changed upon restart. I am using automove, and it is working fine 99% of the time

See if this helps: http://lime-technology.com/forum/index.php?topic=53689.msg517002#msg517002 Thanks for that I had it to SMB2, and changing it to SMB2_02 fixed it. I have been running with _02 before. Just read somewhere that SMB2 should be fine, guess it was not.

Anyone experience slow read from unraid when using the Turbo Write? I get 100+MB/s when i write to unraid (Without cache), but it swings from 50-100 when reading from unraid.

Refresh the webui is usually enough

You can just add the tracklabels plugin to your docker data folder. I did that, since I was missing the plugin.

Anyone got it to work with pipework? I have management working, but dns does not seem to work. EDIT: Nvm, I figured why and how Apparently when using pipework, it creates the adapter eth1 and not eth0. I just created another .conf file with "interface=eth1" and problem was solved

What speed do people get when running unbalance? Mine seems pretty low 35-45MB/s

i really wish i could say yes, but sadly no, the only option you have is to always ensure you start any of my VPN dockers only after you have started your VM, im going to for now create a simple entry in MY go file that executes a 'docker start <containername>' after i see my VM running and use that instead of the autostart option in the docker UI. i have discussed this with jonp a couple of times but sadly ive seen no real fix included in any of the releases. I found a fix Just add this to your go file: /sbin/modprobe iptable_mangle

so ive spotted you have incorrectly defined your LAN_NETWORK, snippet:- LAN_NETWORK defined as '192.168.88.12/24' it should be (assuming you have the CIDR correct as well):- 192.168.88.0/24 So correct this first, once you've done this if its still not working then post screenshots of the unraid docker config for this container. Also create a env var with name DEBUG and set the value to true and post the supervisord.log again. oh and change your password, youve included it in the log. I usually have it to 88.0/24, but I was just trying things out. I have attached screenshots and new log OK well that log now shows a successful start, so you cant now connect on http://<unraid host ip>:9080 on your home LAN (not over internet)? Hmm this was super weird. Earlier when i troubleshooted this, i was on a vpn to my home network. Rutorrent didnt work, and neither on my NAT forwarding. But it is working at home now. NAT forwarding may not work (depends how this is configured), due to a bug in unraid where they dont enable iptable mangle support until you enable a VM, then it all magically springs into life. snippet from your latest log showing this:- 2016-11-28 16:06:46,331 DEBG 'start-script' stdout output: [info] iptable_mangle module not supported, attempting to load... 2016-11-28 16:06:46,332 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.4.30-unRAID 2016-11-28 16:06:46,332 DEBG 'start-script' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to rTorrent webui or Privoxy outside of your LAN But it should work fine inside your LAN, so not sure what your issue was before. That makes perfect sense, since my vm was turned off. Turned them on, and restarted rtorrent, and NAT are now working. Any way to turn that module on permanent?

so ive spotted you have incorrectly defined your LAN_NETWORK, snippet:- LAN_NETWORK defined as '192.168.88.12/24' it should be (assuming you have the CIDR correct as well):- 192.168.88.0/24 So correct this first, once you've done this if its still not working then post screenshots of the unraid docker config for this container. Also create a env var with name DEBUG and set the value to true and post the supervisord.log again. oh and change your password, youve included it in the log. I usually have it to 88.0/24, but I was just trying things out. I have attached screenshots and new log OK well that log now shows a successful start, so you cant now connect on http://<unraid host ip>:9080 on your home LAN (not over internet)? Hmm this was super weird. Earlier when i troubleshooted this, i was on a vpn to my home network. Rutorrent didnt work, and neither on my NAT forwarding. But it is working at home now.

so ive spotted you have incorrectly defined your LAN_NETWORK, snippet:- LAN_NETWORK defined as '192.168.88.12/24' it should be (assuming you have the CIDR correct as well):- 192.168.88.0/24 So correct this first, once you've done this if its still not working then post screenshots of the unraid docker config for this container. Also create a env var with name DEBUG and set the value to true and post the supervisord.log again. oh and change your password, youve included it in the log. I usually have it to 88.0/24, but I was just trying things out. I have attached screenshots and new log rtorrentvpn.zip

My rutorrent suddenly doesnt work. Was working fine yesterday. Tried to re-deploy it several times. Also tried to boot up a deluge, just to see if that would work, but same result. supervisord.zip

Go to the docker page and switch the advanced view on and make sure you haven't got any orphaned containers anywhere. There were one earlier, but I removed it OK, well remove Plexpy, remove any orphan container, and rm -rf /mnt/user/appdata/plexpy/ also when mapping your volumes instead of using /mnt/user/appdata/plexpy/ try using /mnt/diskx/appdata/plexypy/ Where x is the disk number that your appdata is on. It did not work. I even tried to create it again, but changed the name and appdata path to "plexpy2". Same result

Go to the docker page and switch the advanced view on and make sure you haven't got any orphaned containers anywhere. There were one earlier, but I removed it