• Content count

  • Joined

  • Last visited

  • Days Won


ken-ji last won the day on August 17

ken-ji had the most liked content!

Community Reputation

44 Good

About ken-ji

  • Rank
    Advanced Member


  • Gender
  • Location
  1. * Yes, you can run multiple docker networks. what is important and not allowed is to have multiple docker networks with the same gateway address * --parent is mandatory as it tells docker where to attach the macvlan network.
  2. Ubuntu mount (NFS) from unRAID

    see this:
  3. [SOLVED] WANTED: cron scheduler docker

    There's a plugin call User Scripts. It'll help you manage script files on the flash drive along with scheduling on when to run them. This will let you do what you want without having to mess with dockers But the script on pfsense is probably the real right way to do it.
  4. No network access (SOLVED)

    Disconnect unRAID by pulling out the lan cable first. Then try to ping the unRAID IP. That'll quickly let you know if anything else is using unRAID IP.
  5. General Port/Forwarding Questions

    Please refrain from setting unRAID IP to a DMZ. That will only invite more security issues - possible worst case for a home user - all files deleted/ransomed, then the unRAID server is used as a jumpbox to further compromise more stuff in your home network - including your router That warning said. DMZ of unRAID for dockers won't work since docker containers by default only have the port that is mapped in the configuration as accessible from outside the host. You probably should post diagnostics, that would show if you have some issues. (Just realized that you failed to mentioned how transmission is installed on unRAID)
  6. Unreliable and Unresponsive

    Run the memtest option on the unraid usb during startup for several hours/passes. This will help rule out memory seating / chip issues too.
  7. Unreliable and Unresponsive

    When unRAID is started up, you can login from the console and type diagnostics the resulting zip file will be at logs directory in the flash drive. If you can't get it via the flash share, you can shutdown unRAID, and pop the USB in another PC to the diagnostics file. I don't think anybody can give you help without anymore details.
  8. how to modify /etc/sysctl.conf on boot

    Well /etc/systcl.conf is just a config file. Changing the contents won't do anything unless sysctl is called again referencing the the conf file But, the sysctl call that does that happens so much earlier in the boot process, so modifying sysctl.conf doesn't help at all.
  9. how to modify /etc/sysctl.conf on boot

    No need, the command just tells sysctl to modify the settings from your new config file, while the normal bootup scripts would have already used the standard config file to set up much earlier on in the boot up process. you could actually just invoke sysctl -w setting=value multiple times in the go file, but this way there will be just one other file to maintain for tweaks later on
  10. how to modify /etc/sysctl.conf on boot

    You can do it they way I do Place the new lines in a new config file somewhere in the usb, then modify the go file to execute /sbin/sysctl -p /boot/config/sysctl.conf
  11. Linux is case sensitive. change the fstab in Mint to match the shares in unRAID. ie ->
  12. Run cat /etc/exports exportfs -v on the unRAID server. This will show us which and how your shares are exported
  13. #1 is a known fault of the unRAID Web UI as it has some (braindead) rules on how the docker webui should be configured #2 is because the dockers can't reach unRAID anymore. You're best solution is to either #1 setup a new VLAN (seeing as you have switch support) and route them together (you have a L3 router right?) This will require resetting up just about everything and your SMB paths might still not work right. - Blame the protocol for this. #2 use two NIC ports like I specified above, and migrate your docker network to the 2nd NIC: Take note to assign unRAID an ip to eth0/br0 and DO NOT assign an ip to eth1/br1 shutdown all involved dockers (do not stop the docker service) execute docker network rm ~docker-network-name-here~ docker network create ... --parent eth1/br1 to regenerate the docker network on the other NIC
  14. IP change on container

    Just my 2 bits: pipework was the docker ip solution before the macvlan system was developed. With docker macvlan solution, pipework is technically deprecated (and is a rather convoluted solution mind you) That said, the macvlan solution has a security feature that is a bit annoying if you only have one NIC on your unRAID machine and no VLAN capable switch/router, as it will prevent your containers from talking to unRAID
  15. Hi, Just my guess after having run vSphere in a domain where the domain controllers are also VMs under the same vSphere instance in a production environment. A lot of scaffolding is present and is a directly supported configuration. ( We almost had a lot of fun when the entire datacenter/environment was powered down for physical relocation ) unRAID doesn't really have all the bits and pieces necessary to support such a setup. I'd really suggest this though. Your domain should have more than one controller. Run one of the controllers on bare metal (or another vm platform), the other under unRAID (if you want.) This would allow everything work even if the unRAID server needed to be rebooted, maintenance etc.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.