surfshack66

@Djoss I see that sound support is added, however, I don't see /dev/snd as an existing path on unraid. Is sound possible for this container on unraid, or do the instructions for "Sound Support" pertain to other docker hosts?

Any particular reason this container is ignoring configuration defined in rtorrent.rc? Despite setting variables in the rc file, this container defaults the global max upload and download rates.

I did that based on this recommendation. Let's try that test you just mentioned. I think you solved it! A quick test from a container in br0.80 subnet I can't believe that script was the reason I was having issues. Thank you so much for helping. Does everything seem right now if I delete that script?

I have this custom script since entries in the routing table don't persist a reboot.

I can reach the gateway

Sorry about that. I said before to ignore br0.100 since I created that as a test. In any case, I cleaned up the test VL100. Unraid is 192.168.1.2 in the LAN 192.168.1.0 Unraid cannot ping containers in other networks. Also, I don't think I have IP addresses on all the VLANs. Is this screenshot what you mean by having IP addresses on the VLANs?

Which screenshot shows default route to 192.168.1.1? This is my LAN network. I just recently moved unraid to VL100 as a test to see if the issue persists. VL100 = 192.168.100.1

Thanks for joining. I really appreciate it. I pulled you because I read one of your posts from a while back but having an issue despite configuring everything correctly. The issue is unraid cannot ping other subnets and vice versa.

@ken-ji If only things were simple. So I have the VLANs and Custom Networks defined per the attached screenshots, but still having this issue. Ignore br0.100 in the custom networks. It's the same network as br0 and I created it for testing.

@ken-ji I've been reading multiple forums posts, including this In this post, you say: "With only a single NIC, and no VLAN support on your network, it is impossible for the host unRAID to talk to the containers and vice versa; the macvlan driver specifically prohibits this." My question is how do I get the host unraid to talk to the containers and vice versa IF I have VLAN support on my network?

I'm not sure I follow what the means exactly. Are you saying the "issue" I'm having is expected behavior?

Hopefully the title isn't misleading. I moved unraid into a new interface called br0.100 and having the same issue. It seems that no matter what network unraid is in, it cannot ping other networks.

Hi - I'm having a very basic routing issue for my LAN/br0. The unraid server can get out to the internet but it can't ping devices in other networks. What are some basic first steps I can take to troubleshoot this, since I've been unsuccessful in trying to solve this? I think it has to do with some config on unraid. Note: I don't see any traffic/denies on the firewall either.

I have elasticsearch and kibana running but not pointing any logs to it yet. Ultimately, I'd like to use Beats, so I have a Metricbeat container but also not fully configured yet. I don't think I ever solved this either... This project has taken a back seat for some time but I'd like to get this up and running soon.

Hello All - I'm trying to move my server from the lan to a vlan. Currently, the networks are defined on unraid as lan = br0 and vlan = br0.70. Do I need to delete the custom interface on br0.70 before moving the server? If I move it to vlan70, unraid will consider this br0, correct? EDIT: Asking because even though br0 is defined in the routing table and listed under custom networks on docker settings page, I cannot select br0 as a network for any containers. If I move the server to vl70 and it becomes the new br0, I still need to assign containers to that network but currently won't be able to.

I need to change the IP address of this container as well as the connected mariadb container. What's the proper procedure to do this? EDIT: Solved

I have a number of user-defined networks, which I then assign to containers depending on what vlan I want them to be in. I've noticed that containers use the DNS server defined in Settings->Network Settings. After some research, I found that I can define the DNS server per container. https://docs.docker.com/v17.09/engine/userguide/networking/default_network/configure-dns/ Can you add a field in the Docker Settings page to define DNS as well, instead of defaulting to the DNS server defined for unraid?

Any glaring issues? I tried looking through the diagnostics myself but nothing stood out.

Of course! Thank you. tower-diagnostics-20190304-1207.zip

I'm having an issue with SMB and despite reading most of the forums posts/threads about this common issue, I believe the error I'm receiving is slightly different. I have a Windows 10 VM that I am unable to copy files to unraid. I can access the shares just fine, even if they are marked private, however, anytime I try to copy a file from the Windows 10 VM to unraid I'm presented with the following error. 0x8007003B “An unexpected network error occurred” Does anyone have experience with this? Also, this issue isn't just related to Windows 10...I have a Windows Sever 2016 VM running with the same issue as well. Any help would be appreciated..even if its just someone willing to bounce ideas off of.

Running into this error related to permissions. 2019-02-28T20:40:55.049-0500 ERROR instance/beat.go:911 Exiting: error in autodiscover provider settings: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.22/containers/json?limit=0: dial unix /var/run/docker.sock: connect: permission denied Exiting: error in autodiscover provider settings: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.22/containers/json?limit=0: dial unix /var/run/docker.sock: connect: permission denied This is a Metricbeat container running on host network. Essentially following the references https://www.elastic.co/guide/en/beats/metricbeat/6.6/running-on-docker.html Some of the solutions I have found online say "add the current user to the docker group", but I'm not sure how to do that or if it even applies on unraid. Is anyone familiar with this error and how to resolve it?

Graylog provided a list of "quick-start" commands to run their docker. https://github.com/Graylog2/graylog-docker $ docker run --name mongo -d mongo:3 $ docker run --name elasticsearch \ -e "http.host=0.0.0.0" -e "xpack.security.enabled=false" \ -d docker.elastic.co/elasticsearch/elasticsearch:5.6.12 $ docker run --link mongo --link elasticsearch \ -p 9000:9000 -p 12201:12201 -p 514:514 \ -e GRAYLOG_WEB_ENDPOINT_URI="http://127.0.0.1:9000/api" \ -d graylog/graylog:2.4 Could I just create a terminal session on unraid and run these commands? If not, they also provide a docker-compose file. Would it be better to customize this and is it possible to run a docker-compose file?

Sounds like a nice-to-have feature. How would I know if a disk is unmountable because of a corrupt file system vs a different reason?

@jonathanm I think the warning message was fine. It's the first line that confused me. "Format will create a file system in all Unmountable disks, discarding all data currently on those disks." My replacement disk was Unmountable so I read that and formatted. Also, the comment above is confusing... "When a disk is unmountable you need to run a filesystem check, not format..."

Hmmm.. I see now. Thanks @trurl for the explanation.