bukweet

Bingo-bango-bongo! That did the trick. Thanks heaps for the explination.

Yeah, I was kind of picking that up from the linux/arm64/v8 bit of the error message, and started trying different tags because of it. For example I've tried this one: docker pull python:alpine3.13 and it gets me to the same error. From what I can tell, and please tell me if I'm wrong, this image is for amd64, yes?

I wanted to post this is in the Docker Containers forum but it looked like that is more aimed at Community Apps? Let me know if this is in the wrong place. Anyhow, I've got me this docker image that runs a python app. It works just fine on my local machine, but when I pull it down to my unraid server I can't get it to run. Here is the log that the container spits out: WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64) and no specific platform was requested standard_init_linux.go:219: exec user process caused: exec format error I'm using the official python docker hub image for the base containers. In trying to troubleshoot I've rebuilt with a few different ones: rc-alpine3.13, alpine3.13, and am currently using python:3 I've gotten the same error message with all base images. Here is the current Dockerfile FROM python:3 WORKDIR /cord COPY requirements.txt requirements.txt RUN apt-get update RUN apt-get install libffi-dev -y RUN apt-get install build-essential -y RUN apt-get install ffmpeg -y RUN pip3 install -r requirements.txt COPY . . CMD ["python3","bot.py"] I'm all out of google searches and any help is appreciated, thanks!

Hello there, I have been having this issue since starting to use unRAID. My frame rates will drop into the single digits when looking around in games, no matter what the graphics settings are. I've gone through multiple vms and operating systems (mostly Windows 10 and Pop OS) and I can't seen to shake it. With my latest vm, I once again followed the good word of Spaceinvader One's videos on installing a Windows VM and advanced GPU passthrough - > https://www.youtube.com/watch?v=miYUGWq6l24 and https://www.youtube.com/watch?v=QlTVANDndpM I got the ol' gal all spun up and enthusiastically installed Steam and then Rust as I am admittedly a glutton for punishment. Alas, I immediately began experiencing the fps drops when looking around. Here is a gif where I am just moving the mouse slowly from side to side to looking around -> https://imgur.com/Z0n2kjg I have had this issue with Rust, Hell Let Loose, and Minecraft. Funny enough, I experienced none of the issues in Minecraft when I installed it on Linux. I am at a loss as to what to do here as what seems to work for most, does not for me. Here is what hardware I am working with and the xml of the latest vm. Many thanks. Hardware: Ryzen 7 2700x Asus ROG STRIX X470-F GAMING 32 GB RAM Nvidia GTX 680 XFX Radeon RX 5700 XT THICC2 (for gaming) <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='10'> <name>Windows 10.3</name> <uuid>6734d1ac-4d4c-07e3-eb25-fb36eb33ac06</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='10'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='12'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='13'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/6734d1ac-4d4c-07e3-eb25-fb36eb33ac06_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='10' threads='1'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10.3/vdisk1.img' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d5:74:ed'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-10-Windows 10.3/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='0x0c' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/Navi 10.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x028e'/> <address bus='1' device='4'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc082'/> <address bus='1' device='2'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0xa0cd'/> <address bus='5' device='2'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b05'/> <product id='0x1872'/> <address bus='1' device='3'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

BAM! I got it all back! Disks, vms, dockers, everything! For any other poor soul who needs it: I plugged my unRAID flash drive into my laptop and copied all of the files onto my desktop. Among the files is a log directory containing zipped diagnostic files. I unzipped the most recent one. I then did a fresh re-install of unRAID onto the flash drive as instructed by itimpi. Once unRAIDs GUI came up, I was able to re-register unRAID using the link to my registration key file that was sent to me when I purchased unRAID. I was then able to use the file names in the 'smart' directory to match up my drives to the disk numbers as instructed by Frank1940. This let me assigned my disks to the correct disk numbers in unRAID. Upon starting the array, everything was back. itimpi: Lesson learned about backing up unRAID. I will check out the CA Backup plugin that you mentioned. Frank1940: As far as parity disks go, I have just bought the hard drive that I will use for this. I can't thank y'all enough, cheers!

Well, dang it:( Sadly, there are no back-ups. However, when I purchased unRAID, I was emailed the link to my Unraid Plus registration key file. Upon clicking the link, a Plus.key file is downloaded to my computer. I imagine (hope) that the drives are still intact and just wondering who turned out the lights. As far as disk assignments go, I was digging around in the diagnostics files created by unRAID and I found the files shown in the attached pics. The 'smart' directory at least shows the disk name (sda, sdb, etc...) and there is further info for each such as the size of the disks in the file itself. This would not be to hard to match up to the 'df' output I also found shows where each drive was mounted in /mnt. Good Lord, many thanks for taking the time to help here...

Uh-oh. These are the only files that were on the flash drive:

itimpi, Awesome! I was just plugging the flash drive into my lap top to check out the logs! I have backed up the entire contents of the drive and will recreate it as you suggest. To be clear, the config unix executable is the only file that the recreated drive will need to restore my previous settings? Heaps of thanks!

Google searches I did for this did not yield anything that helped. Most issues I found seem to stem from an update. In the search results, people were actually getting some output, where as my system is stuck on a loop in the Unraid boot screen. How it happened: I had been having some trouble with a vm freezing up on me, so I did a force stop from the Unraid GUI. The GUI went a little wonky for a moment and was displaying what looked like a couple of linux logs. These 'logs' were rendered over the GUI and overlapped each other; like the 'logs' were printed out over on top of one another. I should have taken a screenshot of these phantom logs, but alas, I panicked. The only thing I can remember is that they referred to some lib modules. In my panic, I did a hard shutdown of my computer and upon reboot, the Unraid boot screen was stuck in a loop. What it's doing: Here is a video of what it is doing --> https://imgur.com/1PebNA1 I'll select any of the boot options and the whole thing just starts over. The Memtest works and succeeds. Hitting tab gets me to the cli, but I'm unsure of what to do here and am admittedly a little wary as I reeeeeally don't want to break it more. Hardware: Ryzen 7 2700x Asus ROG STRIX X470-F GAMING 32 GB RAM Nvidia GTX 680 XFX Radeon RX 5700 XT THICC2 Please hit me up with any questions. Any help is greatly appreciated and many thanks in advance.