Rdhuff1985

Members
  • Posts

    12
  • Joined

  • Last visited

Rdhuff1985's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. 6.12.rc8 but this has been a thing for me since 6.9.xxx. Question: Docker custom network not showing as an option (one that is actually tied to a nic) Custom Docker network br.2 (eth2) will not show up for my docker containers. I have it checkmarked to be available to the docker services in docker settings. I have host communications enabled. I have the motherboard NIC used as the unraid connection. I have a 2x2.5gb nic in a pcie slot. one port is a straight connection from my server to my windows pc. the other, eth2, I am trying to use for a camera setup. I have interface eth2 bridged to itself. I have tried it bridged to itself, bonded to itself, bonding and bridging disabled. I was able to get it to pop up, briefly, after I realized my IOMMU groups werent available due to a bios update I did. I reenabled Intel Virtual stuff in the bios, and when I rebooted(after rebuilding my docker image bc enabling that corrupted my docker image) the network was available. I needed to reboot before I could implement it with the docker I wanted, and then it disappeared never to be seen again. I have cheated this, but it doesn't work as I want. I bridged eth2 to itself, and ran: docker network create \ --driver=bridge \ --subnet=172.17.0.0/24 \ --gateway=172.17.0.1 \ br2 This made the docker network available, and even brought up the name I had named it. but what it did was connect as if it was br0 and not br2. Any help, or if you need any more information, that would be great and I will provide it if I can.
  2. I just blew apart my unraid server to try and get my docker networks working correctly. They now work, but I noticed when I was mass updating my docker containers from the app tab, using the "previous installed" tab and checking all my previous containers, it hangs on the last container. It actually installs everything just fine, but the pop up will not clear, nor ever say done. the page is unusable in that state, and you have to click over to another tab. If I posted in the wrong area, please let me know. I searched for this topic and it did not show up. running 6.12.0-rc7
  3. OK. So as of right now, what I did was delete my vdisk file of my docker container. Then, I went into bios and re-enabled the Intel Virtual iommu groupings for my processor. I rebooted, started docker. then I made sure to have my regular docker network that I use already available. For some reason, create user created networks never works for me. When I ran Docker network ls, my custom docker network did not pop up, so I recreated it. Then, I redownloaded all my previous containers from the apps tab. (super easy way of doing it btw). Once that was done, when I checked my available networks for docker, my original issue had gone away. Hopefully, this will help you. Seems to be a roundabout way to fix an issue that shouldn't be an issue, but that is what I did.
  4. No. No solution as of yet. If you find something let me know.
  5. This is 100% my issue. the home/nobody shouldn't even be a thing with /media set up properly in the docker config. I had my host set to user/syncthing and left /media alone for docker path. then my docker image file ballooned to 100% in 10 minutes. Thank you for posting this. this is with Binhex-Syncthing as of 2/16/23.
  6. I have tried it both ways, multiple times, and sometimes at the same time. I've created multiple vlans at once with different settings in each, and no matter what, they are not showing up in network select for the containers.
  7. exact issue I am having. has anyone resolved this?
  8. this is the exact issue I am having right now. did anyone ever get this figured out? (one of many issues, but I did just get my argo tunnel squared away, thanks ibracorp)
  9. I disabled docker on the docker settings page. I then enabled VLANs under the network settings, and created a VLAN and set it to static. set the ip range to 192.168.x.0 - x being the vlan number. I gave it a gateway of x.1. Now back over on the docker settings page, i check the box to include the vlan as a container selection. Enable docker and try to edit a docker to be set to the vlan I just created and it does not show up. FULL TRANSPARENCY - This may not be a bug, it may be user error, but I can not for the life of me find a solution to this issue. I have been trying to get VLANs to work for a cctv setup like spaceinvader shows in his shinobi series. At first the VLAN did show up as a selectable option, but the container would not show up with the webui. I ran "docker network prune", but all my containers were stopped when I ran it, so I lost every custom network I had, including my proxy network. (my mistake I guess). I recreated the custom proxy with the "docker network create" command, and it started showing up just fine again. the bro.x vlan network just will not show back up. I ran this - rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart to try and rebuild my network stack as per a forum post, but it didn't achieve anything as far as I can tell. If I need to move this, I will, but it does seem that if I can create a vlan and choose it to be used with a container, it should show up. I also realize I may have screwed something up.
  10. Figured it out. just had to map a network drive with the 10.10.10.x ip address. thanks SpaceInvader from 4 years ago. Should've known better.
  11. On Unraid server Pro, version 6.10.0-rc5 I have just recently purchased 2 2.5gb nics. one for my windows pc, and one for my unraid server. I still rip from disks, and have been doing tons of 4k. (my interwebs isn't very fast out in the country, fixed wireless) When my SSD on my windows pc gets close to full, I transfer the files over the network. *What I have* PC 1gb nic to unmanaged 1gb switch to router to 1gb switch to unraid 1gb nic. *What I'm trying to do* What I want to set up is 2.5gb nic pc directly to 2.5gb nic on the unraid. on its own subnet. the rest of my house is on 192.168.0.x, and I will be doing this P2P network 10.10.10.x. I want to transfer the files directly over the 2.5gb nics instead of my local network. What am I missing? I can ping the unraid IP from the windows PC, but cant see the windows nic from the unraid machine. I have the windows side of it set to private, also no gateway set, and a mask of 255.255.0.0. Unraid side I have no gateway set, /16 subnet mask. Attached is my network config for UnRaid, I'll also attach my windows settings. network.cfg