wtfcr0w

I decided to forego mounting the docker socket to the LXC and ended up opening up the TCP port to the docker daemon and am connecting to it through ip/port to get all of my containers. Thank you for the help anyway.

I am developing a docker front end dashboard and wanted to see about passing through the socket to use rather than using nested containers. I have plenty of containers on the host machine and didnt really want to run all the same containers in the LXC as well, as I would be using the API's to pull info from the docker containers.

Hey I am trying out LXC containers again and would like to use them for development. I would like to know if it is possible to pass through /var/run/docker.sock from the host machine to a container. Can this be done?

My server locked up and I had to force a reboot by holding the power button down. This has only happened once or twice in the past and I have never experienced any issues after restarting the array. However, this time I am having plenty of issues with Docker when restarting the array. The whole OS is slow. I have a few containers that need to be updated and when I go to update them I get an error and it seems unRAID thinks that the container is still running, so it just removes the container from the list altogether and it will not allow me to add it back. When I reboot, the container is there again but it will not start. I cant even get to the VM page to see if my VMs are started. Can anyone take a look at my diags to see if there is anything they might be able to identify? I am really at a loss. I run all my 3d printers from my unRAID server and at this point I am dead in the water with my business. Any help would be so greatly appreciated!! io-diagnostics-20230214-1145.zip Edit: After trying to update a container, and it fails and disappears, I reboot and it shows up again. When I try to start the same container I receive the following error: Image can not be deleted, in use by other container(s)

Will do boss. I'll report back soon.

It sat there for a good 10 minutes after I was able to reach it via ssh. Checked the terminal output from the machine itself and it just stops at the samba init.

Stuck at samba on boot as well... Reverted back to 6.10.3

Attached io-diagnostics-20221103-1904.zip

I just upgraded from 6.10.3 two nights ago and have been experiencing extremely slow speeds while updating and installing containers, and also viewing/browsing the CA app store. I am not the only one, there is a thread I created on Reddit where others are also experiencing the same issues. Docker container updates and installs sometimes take at least 4 times as long as they used to on 6.10.3. Anyone else experiencing this issue? Thanks in advance

Glad you were able to get it working!! Thanks for laying out a walkthrough for others, as well!!

I setup a Debian virtual machine and used the Kiauh tool to install klipper. I've also had good luck with the Ubuntu Server iso. I wouldnt use the raspberry pi image. Then use the USB Manager tools to forward your printer (I'd recommend forwarding the port) through to the virtual machine so it connects whenever the VM turns on.

Dude you are the f'n man. Thank you so much.

I have a VM running an application called Klipper to control my 3D Printers. I had only one, but now I am trying to add a second. When I try to add both printers to one VM I am receiving the following error when trying to start the VM: operation failed: Multiple USB devices for 1a86:7523, use to specify one And the VM doesnt start. Both of the devices show up as QinHeng Electronics CH340 serial converter (1a86:7523) When I try to add both printers to either my Debian or Ubuntu Server VMs I get the following error while trying to save the VM instance: XML error: Hostdev already exists in the domain configuration Does anyone know of a workaround for something like this? I dont mind having to run two separate VMs, one for each printer. I would just like to have them both controlled by klipper within a VM. I'd rather not have to try replacing a main board on one of them. Thank you for any assistance.

Ever since updating to 6.10.2 I have had an issue where Docker and libvirt will not start with the array after entering my encryption password. I get this error message when attempting to check docker services: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 710 Couldn't create socket: [2] No such file or directory Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 896 Every time I see this I need to recreate the USB disk and start from scratch. And it works for weeks until a reboot, then I have to do the same all over again. Why is this happening? It doesnt happen on 6.10.1 or any of the 6.10 RCs and I cant try another USB device until June 14th when I have the availability to change it out. I've attached diags. io-diagnostics-20220612-0939.zip Edit: After checking docker settings, I see it says the appdata folder doesnt exist. After ssh'ing in and checking, my user folder was not mounted and the only thing in there was the LXC folder. I unstalled the LXC plugin, rebooted and now it's working.

It's definitely enough. I'm thrilled to have even just the Debian lxc working! Thank you so much.

I was able to pass it through and find it in /dev but for some reason I cant utilize the device. Messed around with permissions, probably have to alter udev rules or something. I'll have to play around with it later this evening. Also, when attempting to start Fedora in the foreground I get this: lxc-start -F Fedora Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!!!!!] Failed to mount API filesystems, freezing. Freezing execution. Great job though. I can see this going far!

I found that as well, tried it and no go. As soon as I altered the config file the LXC container disappeared from the LXC page.

I've also tried Ubuntu Jammy and Fedora 36, no dice. Neither of them start.

Understood!! You're awesome for getting this going in the first place. Serious kudos for you. So far I am running a Debian Buster container without any issues. Trying to figure out how to pass through a USB device right now..

Is there a possibility of adding TurnKey containers in the future? https://www.turnkeylinux.org/all

Oh my god I love you so much. You have no idea how much I have been praying for LXC support on unraid. Thank you so, so, so much!

I've upgraded but I cannot boot. Upon trying to boot I am receiving the following error: FAT-fs (sda1): error, invalid access to FAT (entry 0x0995cb33) FAT-fs (sda1): error, invalid access to FAT (entry 0x0995cb33) FAT-fs (sda1): error, invalid access to FAT (entry 0x0995cb33) FAT-fs (sda1): error, invalid access to FAT (entry 0x0995cb33) (this shows up a lot) attempt to access beyond end of device sda1: rw=0, want 51466008072, limit=60618752 attempt to access beyond end of device sda1: rw=0, want 51466008072, limit=60618752 attempt to access beyond end of device sda1: rw=0, want 51466008072, limit=60618752 attempt to access beyond end of device /usr/bin/sha256sum: /boot/bzmodules: Input/output error bzmodules checksum error - press ENTER key to reboot I was ok on RC2, but I rolled back to 6.9.2 and it boots just fine. Anyone have any idea how to remedy this?

Well, I've tried almost everything I can think of. Every type of VM, every type of machine (Q35-X.X), every bios, multiple different bootloaders and OS install files. I cannot for the life of me get xpenology to run on this. I even tried on my mac in vmware and still had issues. Farthest I have gotten is installed the OS .pat file, but every time it reboots it says it needs to recover. Other times it says there was an exception. Other times it says the file is corrupt. If anyone has any knowledge on this whatsoever I would really appreciate it. I used to have xpenology running on proxmox before running unraid and it was so useful to me that I would really like it back just for a few features. I would appreciate any suggestions so much.

I'm sorry to wake a sleeping thread, but I've been working at this for three days now and one time I was able to get the 'diskstation' found on find.synology.com, or the DS Finder android app, but like others in this thread, when trying to upload the DSM_DS3617xs_23739.pat, after using the 1.03b boot image, with a machine type of q35-2.9 (nothing else ever worked) I received the same error saying the file was corrupted. In order for it to be found, or even get an IP on my network I needed to use SATA for both the primary and secondary disks in the VM. Then I tried the 1.04b image with intentions to use DSM_DS918+_25426.pat. I tried using the same settings, and swapped around the machine type a bunch, even tried writing the image to USB and booting the VM with that directly. I cannot for the life of me get this to work. If I need to post my settings I will do, but if anyone has any recommendations I would appreciate it so, so much.

I was not trying to rebuild. The parity drive was bad so I pulled it so I can have it replaced. This morning I forgot that I pulled the defective parity disk and went to wipe it, but since it is the same model/brand as another disk in my array I wiped a disk in my array by mistake. I wanted to try to wipe the parity before sending it back to the manufacturer. I simply wiped a 4TB disk in the array containing movies/TV in a 2 disk array by using fdisk/mkfs.ext4 etc... I do not have access to the files I want to keep because I have not attempted to restart the array as the disk that I wiped by mistake is showing as disabled and I do not want to lose any of my personal data I keep in the shares on the disk that is still in tact. I wanted to make sure I got any advice from the pros here before making any move. Thank you for any help. You have no idea how grateful I am. Diagnostics: io-diagnostics-20210925-1110.zip