Skrumpy
-
Posts
116 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Skrumpy
-
-
Echoing what others have said, thanks for putting this together. A sizeable portion of the community depended on the successor for easy install/update of those.
Going to add my own plug for lftp to be added (I know you're working on getting everything moved over).
I see that fix common problems flags that I have lftp manually added to the extras folder, is it going to freak out when nerdtools does the same?
-
I am running 6.11.0 with an Win11 VM as my system.
I am downloading from a remote box, oddly I get much worse performance when downloading from my unraid shell compared to the VM.
I get 30MB/s DL from Filezilla (unsegmented running in VM) SFTP and only ~18MB/s DL with LFTP running (unraid shell) SFTP with 5 segments? I'm not sure as to why the Filezilla running on the server VM would be so much faster than running in the shell? Is this a network setup issue?
I'm not seeing any overt issues with my setup, they are both going to a cache only SSD, no other processes running. Have tested multiple times and get the same results.
Thanks,
-
I have a fairly simple Userscript script (below) running that lftps files from a remote server then updates permissions so that Sonarr/Radarr can move them. Everything was working well until an update or so ago. Did something change that would prevent this from working? I now have to run docker safe new perms because files come in as root -rw-r--r-- instead of nobody -rw-rw-rw- and sit on the cache drive until it runs out of space and seizes Unraid. Feels like I'm missing something simple here..
#!/bin/bash LOGIN="login" HOST="xxx.xxx.xxx.xx" LOCAL_DIR="/mnt/cache/data/downloads" REMOTE_DIR="/home/deluge/sync/" NFIL=1 NSEG=5 lf=/tmp/syncfiles.lck touch $lf read lastPID < $lf [ ! -z "$lastPID" -a -d /proc/$lastPID ] && exit echo $$ > $lf lftp -u "$LOGIN",placeholder -e "set sftp:connect-program 'ssh -a -x -i /root/.ssh/Key'" sftp://"$HOST":22<< EOF set xfer:use-temp-file true set xfer:temp-file-name *.tmp # set pget:min-chunk-size ${MINCHUNK} set pget:default-n ${NSEG} set mirror:use-pget-n ${NSEG} set mirror:parallel-transfer-count ${NFIL} set mirror:parallel-directories true set mirror:no-empty-dirs true set net:max-retries 2 mirror -c --Move --only-missing --no-perms --no-umask "${REMOTE_DIR}" "${LOCAL_DIR}" quit EOF chmod -R 0777 $LOCAL_DIR exit -
On 5/28/2022 at 7:45 AM, JorgeB said:
May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan] May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
See also here:
Think this may have been the major source if not the total problem. Up 3+ days so far (restarted for something else earlier) without issue.. keeping my finger's crossed. Thanks again!
-
1
-
-
5 hours ago, JorgeB said:
May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan] May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
See also here:
Changed that setting to ipvlan. Hopefully that works! I'll give it a go here over the next few days and see what happens. I'll update the thread if it happens again otherwise I'll mark it as resolved.
Thanks JorgeB for an option to try at least.
-
Diagnostics attached for this last hang. Essentially my system will either completely hang or allow GUI access but be unable to shut down (with docker services stopped/etc) after 1 to several days.
I am running pi-hole docker as my DNS and I believe everything setup correctly. I have my server and router (r9000 running DDWRT) setup for IPV6. From a couple of obscure threads, I have seen that unraid may not handle IPV6 correctly? I was hoping after the last update to rc6.10 that there would be some relief to this issue.
Anyone have any insight. At my wits end on this one.
-
22 hours ago, ich777 said:
Have you tried to switch to Q31-6.1 yet?
Sent from my C64
I updated to Q35-6.1 and latest VirtIO when I upgraded to Win11.
-
13 minutes ago, jaybee said:
So are we saying that the AMD performance hit in games is here forever, if you run a Windows 11 VM with AMD processor? It is not solvable?
I did have a measurable performance (FPS) hit in 2 games that I play (Hunt Showdown & League of Legends), but more in Hunt (consistently ~20ish FPS less) due to how processor heavy of a game it is.
These weren't "scientific" tests, just anecdotal pre-upgrade (Win 10) and post-upgrade (Win 11 full update) game launching and playing for several hours each (no other changes done).
I was able to mitigate most of the performance drop in Hunt by doing some other tweaks in/out of game. It is still not in a pre-upgrade state and I occasionally experience random, quick, infrequent, and severe slowdowns/lag when experiencing visually demanding areas. These did not occur pre-upgrade.
I do slightly regret updating my VM to Win 11 as I have not noticed any significant benefits to updating that make it worth the hassle of trying to mitigate the performance drops and of dealing with it in game.
I do not know how other systems and/or other games may be impacted and can only speak to my own experiences and the 2 games I have tested. I would suggest other people give it a go and see if we can have QEMU take a look at virtualization changes.
Q35-6.1 (latest ver in RC2) already had some AMD "fixes" and perhaps they'll be able to tweak things specifically for Win 11 at some point.
QuoteMany fixes for the emulation of AMD virtualization extensions.
-
17 minutes ago, ich777 said:
I think you can't install a AMD Chipset driver because the Chipset is recognized as Q35-6.1 because it's actually emulated (you can't use the hosts chipset anyways) and not as AMD, I don't think you can change that.
There's an unraid thread here where someone was wondering about the same and someone had mentioned using SEABIOS.
"Right now i have 2 vms running SEABIOS with Q35-4.2 and AMD drivers are installing like a charm and not causing me any headaches."
Do you think the emulation will avoid the performance degradation with AMD processors and Win 11? Otherwise, this may be something to bring to the attention of AMD users prior to upgrading via VM.
-
11 hours ago, alturismo said:
yes i did, sorry, but i meant RC2 and not a final release, im pretty sure you wont regret using it as its a RC and not a Test branch which where the steps before
Thanks, got RC2 & Win 11 installed. However, I'm unable to update to the latest ver (3.10.08.506) of AMD chipset drivers which is required to resolve the Win 11 performance issues. The installer does not recognize my system as AMD and exits.
Running the new OVMF TPM, Q35-6.1, and virtio-win-0.1.208-1 and still no luck. Have also tried the chipset version directly from mb website 3.09.01.140 and still no luck.
Device manager lists Computer as 'ACPI x64-based PC' and Processors 'AMD Ryzen Threadripper 3960X 24-core Processor'
Anyone have a suggestion?
-
1 minute ago, SimonF said:
6.10rc2 is available
Yes, the RC, I thought it was discussed in this thread that the release would be available soon.
-
Any update on how "soon" the next release will be out?
Alturismo posted on Sept 30th;
Quotei can say i made alot of tests with @ich777 and it looks all good to be coming soon (very)
its now a matter to make it as easy as possible due webgui which is also pretty far done, so no manual actions would be needed.
AMD has patched their Win11 bugs so looking to get it going on my rig.
Thanks gents.
-
Was going to use the Zoltan option, but if @ich777 says that may mess things up once it's integrated, I will wait a few more days.
Is this unRAID update allowing pass-through or is everything going to be emulated?
I am currently running a Win 10 VM and would like to just update to Win 11 VM.
-
During gaming my parity (usually) and sometimes another drive will get above normal operating temps. This otherwise only happens during a parity check.
My VM OS and all games are installed to a passthrough NVME dedicated to the VM.
Using unRaid as a daily driver, TR 3960x v6.9.2 with my Win 10 VM xml below. Anyone have any thoughts on why these non-VM drives are getting hot while not utilizing them directly? Also if you're parsing through it, any additional optimization tips would be greatly appreciated.
Thanks!
Spoiler<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>Redacted</name> <uuid>Redacted</uuid> <description>Windows 10 Gaming VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>32505856</memory> <currentMemory unit='KiB'>32505856</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='9'/> <vcpupin vcpu='1' cpuset='33'/> <vcpupin vcpu='2' cpuset='11'/> <vcpupin vcpu='3' cpuset='35'/> <vcpupin vcpu='4' cpuset='13'/> <vcpupin vcpu='5' cpuset='37'/> <vcpupin vcpu='6' cpuset='15'/> <vcpupin vcpu='7' cpuset='39'/> <vcpupin vcpu='8' cpuset='17'/> <vcpupin vcpu='9' cpuset='41'/> <vcpupin vcpu='10' cpuset='19'/> <vcpupin vcpu='11' cpuset='43'/> <vcpupin vcpu='12' cpuset='21'/> <vcpupin vcpu='13' cpuset='45'/> <vcpupin vcpu='14' cpuset='23'/> <vcpupin vcpu='15' cpuset='47'/> <emulatorpin cpuset='0,24'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7cfe3c4b-9734-32f6-9850-3497f631d500_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/vm/isos/virtio-win-0.1.196.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='nec-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:75:87:7a'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-MSVM/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/cache/vm/rtx2080ti.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x03f0'/> <product id='0x0970'/> <address bus='3' device='3'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc53a'/> <address bus='11' device='22'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bda'/> <product id='0x8771'/> <address bus='9' device='2'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1038'/> <product id='0x1290'/> <address bus='11' device='25'/> </source> <alias name='hostdev8'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1038'/> <product id='0x1297'/> <address bus='11' device='26'/> </source> <alias name='hostdev9'/> <address type='usb' bus='0' port='5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0226'/> <address bus='11' device='21'/> </source> <alias name='hostdev10'/> <address type='usb' bus='0' port='6'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
-
17 minutes ago, ich777 said:
Please update the Container and try it again, I changed something and now it seems to work, they changed more then initially thought, but sometimes the server just starts fine and sometimes not...
I deleted docker & folder, then reinstalled. Running multiple versions so no need to update SteamCMD files and delete the entire image right?
0.9.4 (the basic pull from the docker for V+ = true) worked fine without issue. When I copy & paste the 0.9.5 unix server files into the docker and overwrite I still get the error.Spoiler
-
1 hour ago, ich777 said:
What issue exactly?
Nothing of both, it has nothing to do with Unraid and the last Docker update was made 7days and 10hours ago since my container updates the game and ValheimPlus itself on every start/restart.
Are you sure?
I now tried it also with the default settings and enabled Valheim+ (that's the only thing I changed) and this is the log output: valheim.log
And I also think that Valheim+ is working (never actually used Valheim+ before):
EDIT: Please do the following steps:
- Delete the Container
- Delete the 'valheim' folder from your 'appdata' directory
- Grab a fresh copy of Valheim from the CA App
- Set Enabel ValheimPlus to 'true' (without quotes)
You can change all other values later on...
Please also make sure that your share where the folder 'valheim' is located is set to use the cache "Only" or "Preferred" otherwise the Mover will completely mess up the game and it won't even run anymore...
Good news.. I knew I wasn't going insane!
Thanks for verifying with me so I could go back to them and tell them it wasn't the docker they wanted to blame it on! -
13 minutes ago, ich777 said:
What issue exactly?
Nothing of both, it has nothing to do with Unraid and the last Docker update was made 7days and 10hours ago since my container updates the game and ValheimPlus itself on every start/restart.
Are you sure?
I now tried it also with the default settings and enabled Valheim+ (that's the only thing I changed) and this is the log output: valheim.log
And I also think that Valheim+ is working (never actually used Valheim+ before):
EDIT: Please do the following steps:
- Delete the Container
- Delete the 'valheim' folder from your 'appdata' directory
- Grab a fresh copy of Valheim from the CA App
- Set Enabel ValheimPlus to 'true' (without quotes)
You can change all other values later on...
Please also make sure that your share where the folder 'valheim' is located is set to use the cache "Only" or "Preferred" otherwise the Mover will completely mess up the game and it won't even run anymore...
Yes, it is on cache only. It must be something with their 0.9.5 files as I have tried the above process (and other variants for the past 8 hours without any luck.
It's odd, because the same error happened to someone who was using the 0.9.4 files and in a different docker environment. Which is what made me think there may have been another change.
The V+ dev said the only change they did was put some " into the start server/game.sh, however, I tried just copy & paste the 0.9.4 sh files and same issue. Must be something else they'll have to sort out.
Thanks for looking into it at least and I'll report back if I find out anything else.
-
22 hours ago, gastr0 said:
Apologies if this a simple error on my part. First time adding a game server (Valheim). Clean install of the docker, default settings, both server and steamcmd paths set to the cache (no move).
I keep getting the same error from the server log...last two lines below. I've let it run for approx 3 hours, this sequence repeats but the server itself doesn't seem to start. I haven't manually changed any of the files (eg. start-server.sh)
---Checking if UID: 99 matches user---
usermod: no changes
---Checking if GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
usermod: no changes
---Checking if GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.
Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
---Update Server---
---Update Server---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.
Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
Success! App '896660' already up to date.
---Prepare Server---
---Server ready---
---Starting Backup daemon---
---Start Server---
/opt/scripts/start-server.sh: line 140: 60 Killed ${SERVER_DIR}/valheim_server.x86_64 -name "${SRV_NAME}" -port ${GAME_PORT} -world "${WORLD_NAME}" -password "${SRV_PWD}" -public ${PUBLIC} ${GAME_PARAMS} > /dev/null22 hours ago, ich777 said:Can you try to stop the container delete the valheim directory that is located in your appdata, then also delete the container and after that try to redownload it from the CA App and see if it works with the default settings?
Having the same issue.. anything to do with the recent update to 6.9.1? Docker get updated? I was trying to install the 0.9.5 alpha to do some testing.. but getting the issue below. I have tried deleting, reinstalling, default settings, etc. Here is the pastebin of my log https://pastebin.com/ecGCk8mt and just sent you the alpha 0.9.5 files of V+ for unix server/windows client in the event you want them.
RecordSteamInterfaceCreation (PID 75): SteamNetworkingSockets008 / /opt/scripts/start-server.sh: line 140: 75 Aborted ${SERVER_DIR}/valheim_server.x86_64 -name "${SRV_NAME}" -port ${GAME_PORT} -world "${WORLD_NAME}" -password "${SRV_PWD}" -public ${PUBLIC} ${GAME_PARAMS} > /dev/null
Another user trying to install from Debian having issues as well...
-
@ich777 I came across this compression mod, but something is going on and it is not working.
Speaking to the mod dev, I have installed BepInEx (FULL) over the client/server to update that. I also have V+ installed. I can connect fine with these 2 changes.
Then I install his mod (server + client) but not getting to connect. Anything you see right off the bat that may be a cause?
He's not seeing where things would be stopped on the mod DLL end. The mod config log shows it is enabled. Unfortunately I can't see the console as web console doesn't show anything.
This mod could be pretty big for reducing server lag and wanted to test it out. Not sure what could be the issue here.
https://valheim.thunderstore.io/package/Seb/SebNetCompressionPlugin/ -
9 hours ago, jonathanm said:
That presupposes full root access to the server, not just
Thanks guys, just used the openssh docker and added the other docker container path as access to that path. Seems to work.
Just need to figure out how to add multiple users in openssh docker as it only has variables for a single user.
-
53 minutes ago, ich777 said:
You have many ways to connect to the container over SSH through your Unraid server:
- Connect to your server via SSH
- docker exec -ti Valheim /bin/bash
- su $USER
With this commands you are in the "user" shell of the container.
A user.sh script is actually a strong tool, this runs as root on every start of the container and you can basically install everything inside the container to create a connection what you want.
For example a SSH daemon, TELNET, or whatever you can imagine, you even can write a script that waits for inputs but as said I don't know how such a Discord bot works and what kind of input our output it needs...
I think we got it setup, appreciate the help!
-
1
-
11 minutes ago, ich777 said:
What is similar?
Should be possible but you have to write a user.sh script that will execute at the startup of the container.
I don't know much about Discord bots and how they work...
Just any other way to provide remote access to the docker container. Just a a user.sh script that has what kind of command to allow access?
-
Running a game server docker and looking to allow SSH/telnet access (to that docker only) so that we can have a Discord script update a single text file (whitelist to allow game server access).
Hopefully there is an easy way to do something like this or similar. Searches haven't really shown much. I'm assuming it is not as simple as adding a TCP port to the container and adding that port to the router?
Anyone have any solutions?
-
@ich777 any idea of how I can allow SSH (or similar) access to a game server docker? For the Valheim docker I would like to be able to allow our Discord bot to modify permittedlist.txt so that we can automate the SteamID whitelisting process (so I don't need to be there to manually add them).
Any ideas? I'm assuming it is not as simple as opening a TCP port on the docker itself?
[Support] Unbound
in Docker Containers
Posted
Has anyone been able to get Unbound to work on 6.11.5 using the auto-trust-anchor-file: "/opt/unbound/etc/unbound/root.key" file? I have the file in the unbound directory, but no matter what permutation I use for the anchor file or chroot (including chroot: "") I'm not able to get it to start (without the root.key file it works fine). ChatGPT can't even figure it out! I saw an old Reddit post about adding in 'username: "_unbound" into the unbound.conf but not even that is working.
# unbound-anchor -a /opt/unbound/etc/unbound/root.key [1681261500] libunbound[80:0] error: failed to read /opt/unbound/etc/unbound/root.key [1681261500] libunbound[80:0] error: error reading auto-trust-anchor-file: /opt/unbound/etc/unbound/root.key [1681261500] libunbound[80:0] error: validator: error in trustanchors config [1681261500] libunbound[80:0] error: validator: could not apply configuration settings. [1681261500] libunbound[80:0] error: module init for module validator failed