mega

I cant get the app to load properly, even with default settings in the docker setup. It appears it cannot make files in the appdata folder for some reason. Docker made the unraid appdata/carvey directory, but there is nothing inside it. copy from console below. ▲ Next.js 16.2.4 - Local: http://localhost:3000 - Network: http://0.0.0.0:3000 ✓ Ready in 0ms ⨯ Error: EACCES: permission denied, mkdir '/app/data/uploads/vehicles' at n (.next/server/chunks/891.js:333:2092) at k (.next/server/chunks/891.js:1:715) at o (.next/server/chunks/891.js:166:24) at h (.next/server/app/page.js:22:10255) at stringify (<anonymous>) { errno: -13, code: 'EACCES', syscall: 'mkdir', path: '/app/data/uploads/vehicles', digest: '3610851560' }

I have found out what is going on with network and this container. The container is not correctly editing the resolv.conf file fast enough and DNS just breaks. I have found that i have to change the nameserver in /etc/resolv.conf from "nameserver 127.0.0.11" to "nameserver 1.1.1.1" then it starts loading, it appears the DNS/resolv.conf update script triggers AFTER it starts the connection to a VPN server, so without working VPN before the script updates resolv.conf DNS is broken forever. Is there any reason for this, and are any other people having the same issue? I have pasted some info from the container Log below so people can see where it breaks. 2025-06-12 00:53:16.581378 [debug] Having issues resolving name 'ca-toronto.privacy.network', sleeping before retry... 2025-06-12 00:53:21.674007 [debug] DNS operational, we can resolve name 'ca-toronto.privacy.network' to address '179.61.197.44 191.96.36.209 191.96.36.210' 2025-06-12 00:53:21.775482 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '104.18.40.93 172.64.147.163' 2025-06-12 00:53:21.879617 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167' 2025-06-12 00:53:21.908167 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS... 2025-06-12 00:53:21.926360 [debug] # Generated by Docker Engine. 2025-06-12 00:53:21.926396 [debug] # This file can be edited; Docker Engine will not make further changes once it 2025-06-12 00:53:21.926402 [debug] # has been modified. 2025-06-12 00:53:21.926406 [debug] 2025-06-12 00:53:21.926409 [debug] nameserver 1.1.1.1 ***(CHANGED FROM "nameserver 127.0.0.11" TO GET DNS TO WORK)*** 2025-06-12 00:53:21.926414 [debug] options ndots:0 2025-06-12 00:53:21.926417 [debug] 2025-06-12 00:53:21.926420 [debug] # Based on host file: '/etc/resolv.conf' (internal resolver) 2025-06-12 00:53:21.926423 [debug] # ExtServers: [100.100.100.100] 2025-06-12 00:53:21.926427 [debug] # Overrides: [] 2025-06-12 00:53:21.926430 [debug] # Option ndots from: internal 2025-06-12 00:53:21.950627 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS... 2025-06-12 00:53:21.968717 [debug] nameserver 1.1.1.1 2025-06-12 00:53:21.968753 [debug] nameserver 84.200.69.80 2025-06-12 00:53:21.968759 [debug] nameserver 37.235.1.174 2025-06-12 00:53:21.968762 [debug] nameserver 37.235.1.177 2025-06-12 00:53:21.968765 [debug] nameserver 84.200.70.40

Does anybody else have random DNS issues where you have to switch PIA endpoints 50000 times to find one that works? I am using PIA VPN with port forwarding. Is there any fix to this? What could be causing these DNS issues where it cannot find the PIA IP? Log attachedsupervisord.log

I have the container on its own IP(macvlan), so I would like to use port 80 to connect to it

Does anyone know how i can reconfigure the listen port of the web interface to port 80 instead of using 8080? I can seem to find anything in the appdata files on config for an apache server or tomcat server. The web Port variable in the container does nothing when using a bridge network.

Is there anything else to do if my VM disk is stored on the array? I have 2 VM disks that are 100GB each that I have stored on the array because of their size, and because I do not use them often and I dont care if they operate a little slow. Is there a way to stop the drive they are stored on from spinning up every time I log into the Unraid web UI?

To clarify this a bit. If you are on an Intel iGPU and running into the "Vendor command returned unparseable data." error. Go to "Settings > GPU Statistics" and change the "UI Automatic Refresh / Interval" to the new lowest value of "2000" and change the "Intel_top_command_timeout:" from the old default of ".500 .600" to the new value of ".7 1.3"

Where is the "intel_gpu" timers setting located? im getting the "Vendor command returned unparseable data." after an update recently. Im trying to monitor my iGPU on an i5-9600K.

@ich777 An update has been pushed to the main tpill90 repo that fixes this issue. Im just now noticing that the most recent version from the tpill90 repo is 2.7.0 and this container is running version 2.2.2 which is pretty old. Do you think we could get this container updated to the newest version to help address this issue? I would attempt to update it myself but im not well versed in docker. *EDIT* Nevermind, After reading through how your container works I realized I misunderstood what the "Check for Prefill updates" variable did , i thought that updated the prefilled games, but I now realize its for container updates to the prefill docker images for the latest app version.