Siwat2545

be.90 is on 192.168.90.x it need to be 192.168.90.x Idealy use the same bridge for VM and docker

You have 2 Options 1. Set subnet to 255.255.0.0 2. Change br.90 lan group to be the same as eth0

Looks like your running docker-cli command inside a docker container, try using the unraid terminal instead of container shell Or you could just use passwd -u root to change the password

By default unraid use :latest tag if the user does not specify the tag, however eclipse che does not have any image on that tag instead the image is on the rc tag Sent from my Pixel 3 using Tapatalk

Can you change the repository to eclipse/che:rc Sent from my Pixel 3 using Tapatalk

Try nuking the onlyoffice directory Sent from my Pixel 3 using Tapatalk

Click show more settings and take a screen shot also run tree on your appdata onlyoffice folder and post the output Sent from my Pixel 3 using Tapatalk

Can I have your Container Config page screen shot? Also can you try enabling priverage mode Sent from my Pixel 3 using Tapatalk

Can I see your log and config tree?

Your config is utilizing a plug-in that is not installed please install it by adding the package name in the packages field

Can I have your container log please

Set it to host mode and send me the container log

You could try to fork my Dockerfile and add your custom ffmpeg to it use FROM siwatinc/homebridge_gui_unraid RUN [YOUR COMMAND]

Just change the port to any free one

add libfdk-aac-dev to the end of that box

Add it to apk packages environment variable Sent from my Pixel 3 using Tapatalk

Yea Its my fault I need to edit the [WebUI=

What exactly is the output (error message)? btw set it to 192.168.0.1.3 no 192.168.1.3:80

No change the network type to custom and the IP is (container static IP):80

The default network value must be changed to use its own IP address

Please change your working dir and config dir to /mnt/user/data/unraid/docker/workingdir and /mnt/user/data/unraid/docker/config respectively Also it's a good idea to give adguard container a dedicated ip

Yup I patched my kernel and it is fixed but you should wait for a Linux kernel that fix this reset bug, patching the kernel can be ... Let's say messy Sent from my Pixel 3 using Tapatalk

I'm here son 🙂 BTW did you managed to survive a VM reboot without kernel patch? Sent from my Pixel 3 using Tapatalk

Actually Yes Yes. Yes. --------------------- For those that're wondering, I just clone Unraid-DVB and add "cd /mnt/user/patch/Unraid-DVB/build_scripts/kernel patch -p1 < ../vega.patch to the line before the makefile process compile the kernel (Like in the picture) Then I just copy bzimage-new, bzmodules-new to the flash directoy and change the kernel line in syslinux to use the newly created file *EDIT: If you do attempt this process, I'm not liable if you break you shit If you already broke it, download a new unraid os zip file from unraid.net then copy bzroot and bzimage and bzmodule to replace your broken one

Can I apply patch to the unraid Linux kernel? I'm looking to apply this patch to the kernal Do I need to build unraid from source? or can I just patch the bzimage / bzroot