binarymelon

I'm wondering if someone could help me with the nut container. I'm having an issue when trying to run the organize API. For some reason I end up with many kworker processes completely pegging all my CPU cores at 100%. I'm not sure what the container would be doing to cause this and I'm not sure what I can do to mitigate it.

My camera is no longer working. There are also a few other people that seem to be having a similar issue. No idea if it's specific to the c920 or not. https://forums.unraid.net/topic/135684-octoprint-webcam-logitech-c920-not-working/#comment-1234031

I'm having the same issue. I'm using the Logitech C920.

Ah...6.10.3

Was it pulled? I'm not able to find it in the community app.

I've found I need to tunnel to my unraid server because claiming won't work unless it's accessed on `localhost`. Not sure if claim codes are required using this process, but if not they've never really worked for me. ssh <user>@<your_server_ip> -L <your_plex_web_port_or_probably_whatever_port_you_feel_like>:<your_server_ip>:<your_plex_port> Then you should be able to navigate to http://localhost:<your_plex_web_port_or_probably_whatever_port_you_feel_like>/web/index.html#!/

Anyone have any experience or tips for setting this up behind nginx. Not really sure what I should do to make the webcam accessible remotely.

Is it possible to start this container without the printer? Still waiting for my printer and I'm trying to test my webcam configuration. Edit: Figured it out. Just removed the device mapping in the configuration for anyone who is wondering.

Is privoxy dependent on the `/data` mount? I've noticed on first use it's extremely slow and I'm assuming it's because a disk needs to spin up.

Im experiencing a similar problem with sonarr and radarr. We’re you able to find a solution.

I'm having the issue as well. I'm not sure it's related to resizing. The issue for me is most severe when viewing the docker page while on a mobile device.

Anyone aware of any custom mods for java and gradle?

If I upgrade my motherboard and CPU, will my GPU id remain the same?

Just wondering if anyone has any suggestions. I'm having some issues using the shawly build. I'm able to run it and connect to it, but no directories or files seem to be visible from multiman. When I browse to the net0 host the directory is empty. However when I try and create a directory it does get created on the server, but is still not visible from multiman.

That was it, thanks. Is it a bug that those connections aren't blocked for openvpn?

I'm trying to switch over to wireguard, but it seems like I can't connect to the webui while I'm connected to my LAN through a VPN (wireguard to unraid, or l2tp to my gateway). Verified that the UI can be hit from LAN and from unraid server. Is this a limitation of wireguard?

There should be a 'Check for Updates' button on the docker tab. It will check and flag any containers that have updates. After that you can just click 'apply update'. Does anyone know how often the docker images are updated. Feature in the latest beta sounds pretty interesting ('Intro Detection') and I'd like to give it a test.

Ok, it seems to be working as expected now. I have another issue that's tangentially related. I'm also trying to setup a container (nginx) that has both br0 and bridge networks. It looks like there used to be a workaround that allowed this, that has since been "fixed". I'd like to be able to create custom dns entries in pi-hole that point to nginx that proxy to other containers on the bridge network. Here's an old thread with someone who was looking for a similar solution.

The container I'm running with the br0 network is a dns server (pi hole). Will disabling 'host access' prevent the host from seeing the container on the lan, or just direct?

Sure. data-raven-diagnostics-20200424-0923.zip

@bonienl Still seem to have the same issue.

I'm having a weird (to me at least) issue where I'm getting two devices registered with the same IP on my router (Unifi USG 3) after creating a container using the br0 network to assign it an IP on my LAN. After creating the container I have two devices with my server IP and 1 device with the docker IP. 1 of the duplicate IP devices corresponds with the br0 device on the server and the other with a shim-br0 device. Is there anyway I can resolve this? My ESET security software is getting duplicate IPs and ARP cache poisoning attacks warnings as a result. data-raven-diagnostics-20200423-1553.zip

Hmmm, this didn't actually seem to work. My client has read only set to false. I'm not really sure what else to do.

I'm wondering if anyone has a good solution to prevent Sonarr from copying between mounted volumes instead of just moving the files? I'd like to prevent the additional writes on my drives if at all possible.