ken-ji

Members
  • Content count

    475
  • Joined

  • Last visited

  • Days Won

    2

ken-ji last won the day on February 18

ken-ji had the most liked content!

Community Reputation

51 Good

About ken-ji

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Philippines
  1. Deploying unRAID using pxelinux

    License is tied to your USB drive. unRAID looks for a USB device during bootup to read and confirm the registeredUSB drive is present. and by design unRAID stores persistent info in the USB drive. Its kinda like running ESXi. you can have it boot of PXE, but its needs to be able to mount a native datastore early enough to be able to read/write persistent information. I don't know why you want to boot a bunch of storage servers off PXE, it's not like the data on the disks is gonna be flexibly moved around. USB drives are fairly reliable, just get decent branded ones of adequate size 8-16G.
  2. You should be using 6.4.1 as it will make things simpler (unclear from your sig - syas 6.1?) Under the Docker settings (can only change while Array is down) Also refer to:
  3. Individual IP address for a docker

    Docker networks don't talk to the dhcp server on the actual network. It runs its own internal address allocator/dns management system. What you want is to tweak the docker network for bond0 and assign the "DHCP pool" range outside of the one on your actual network. (Its under Settings|Docker - Advanced view) To make static IP reservations, you can still assign it in your pfsense, then fill it in the fixed IP when you edit the container settings
  4. unraid vlan vm only

    I think you can turn on bridging and vlan then attach the VMs to the interface (in this case br0.3) Since there is no IP on br0.3, ssh, the webgui, and shares are unavailable to that VLAN, but VMs and docker containers would still function.
  5. How to setup IPs for dockers?

    You are doing it wrong. You need to delete all the port mappings, and keep INTERFACE on eth0. Then there is a drop-down above the port mappings, where the default is host or bridge. You'll need to change that to br0 or whatever docker network you want to use. I can't give you more detailed examples as I'm on mobile right now.
  6. How to setup IPs for dockers?

    Could be a harmless error, since IPv6 is actually available now and some apps complain about not being able to bind to a port if there is an IPv6 binding. Is the webui for pihole accessible?
  7. How to setup IPs for dockers?

    When using custom docker networks, you need to remove all the Port mapping assignments in the docker config page (might need to use advanced view to get them all)
  8. Can't mount NFS share

    Not to sound condescending, but this info is kinda expected. unRAID clearly documents that user shares are all under /mnt/user which implies that any user share exported over NFS should end up with the /mnt/user/ path Additionally, most people with NFS experience would have remembered to check the resulting /etc/exports file or run exportfs -v themselves to check what the server is exporting.
  9. Can't mount NFS share

    unRAID NFS shares are all under /mnt/user So if you had a fog share you'd need to use unraid:/mnt/user/fog to be able to mount it. As an aside and a pro tip use exportfs -v in the unRAID terminal to see the NFS exported locations as well as their NFS level permissions. And you should read this post for details on the NFS permissions
  10. Stackable cases

    Ah, the DIY version of my setup. Would have gone this route if these parts were readily available at my locality. as it was it cost me a pretty penny to get my parts shipped from else where. but I might go this route if parts were available.
  11. Stackable cases

    Usually the better units will have its own power supply, and a "external" port for receiving the data cable Personally I recommend using an enclosure with a SFF-8088/SFF-8644/Inifiniband/FC connector rather than individual SATA connectors. Avoid anything with just a single or pair of SATA ports, as they use port multipliers which can get very slow during parity checks and rebuilds. Plus most the SATA controllers with port multiplier support have been known to be buggy depending on actual implementation . I'm using the now out of production 8bay Areca 4036, which paired with the LSI-9206-16e, keeps necessary cables down to 1x SFF-8644 In fact, my current server is only housing the cache drive, everything else is on the enclosure, so an outage /cable failure will drop the entire array at once, reducing potential issues.
  12. No DNS for Docker VLAN [Solved]

    I setup my VLAN network in 6.3 (before anybody knew about the custom docker networks) In any case a quick testing on my network indicates, that unfortunately DNS queries will be issued using the IP address of the docker container. so if your container is on a restricted VLAN, it won't be able to make the DNS queries.
  13. instructions are on the topic to modify the go file to auto update the /etc/rc.d/rc.docker file to disable auto network creation and cleanup. (revert to 6.3.x behavior) thus you only need to define your docker network once.
  14. No DNS for Docker VLAN [Solved]

    MediaStore:~# docker run --rm --network containers busybox nslookup www.google.com Server: 127.0.0.11 Address 1: 127.0.0.11 Name: www.google.com Address 1: 2404:6800:4005:809::2004 hkg07s24-in-x04.1e100.net Address 2: 172.217.161.164 hkg07s29-in-f4.1e100.net root@MediaStore:~# docker run --rm --network br1 busybox nslookup www.google.com Server: 127.0.0.11 Address 1: 127.0.0.11 Name: www.google.com Address 1: 2404:6800:4005:80e::2004 hkg12s17-in-x04.1e100.net Address 2: 216.58.220.196 del01s08-in-f196.1e100.net root@MediaStore:~# docker run --rm busybox nslookup www.google.com Server: 192.168.2.1 Address 1: 192.168.2.1 router.way-of-the-blade.com Name: www.google.com Address 1: 2404:6800:4005:809::2004 hkg07s24-in-x04.1e100.net Address 2: 172.217.161.164 hkg07s29-in-f4.1e100.net root@MediaStore:~# docker run --rm --network host busybox nslookup www.google.com Server: 192.168.2.1 Address 1: 192.168.2.1 router.way-of-the-blade.com Name: www.google.com Address 1: 2404:6800:4005:809::2004 hkg07s24-in-x04.1e100.net Address 2: 172.217.161.164 hkg07s29-in-f4.1e100.net hmm. this what I get, so its not clear to me what you mean by not being able to use DNS. Also using docker run without the --rm option will spawn containers that't you'll need to manually clean up.
  15. No DNS for Docker VLAN [Solved]

    its a bit odd. as my containers have this root@MediaStore:~# docker exec Transmission cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 root@MediaStore:~# docker exec NGINX cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 root@MediaStore:~# cat /etc/resolv.conf # Generated entries: nameserver 192.168.2.1 AFAIK, docker actually generates an internal DNS server for containers to use, while the host OS does the actual lookups. These dockers are using custom docker macvlan network

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