-
Support for [laromicas] ROMVault docker container
Thank you for your testing. I will take into account this recommendations.
-
Support for [laromicas] ROMVault docker container
Please send me the xml of your config to try to replicate the error.
-
[Support] Gitea
Hi Guys, I am having issues when running gitea, when run it runs perfectly, but after a while it loses the repositories mapping. In the image you can see that in the first run there is a mapping for repositories and in the second run, this mapping disappeared. It seems to happen when sync repos begin, but I have not been able to replicate consistently. Have you found something similar? I have been trying to access more logs to see what can be happening without success. Note: I have several other docker containers with the same volumes and it only happens with gitea and the repositories volume. Thanks in advance.
-
Support for [laromicas] ROMVault docker container
DATVault has problems running in linux, GordonJ has made really good progress to fix this,. The container is already using NoVNC, I fixed the the windows handling and I 'm testing with Ubuntu to fix the text, right now the docker is in alpine and there is some fonts issues it seems.
-
laromicas changed their profile photo
-
Support for [laromicas] ROMVault docker container
Application Name: ROMVault Application Site: https://www.romvault.com/ Docker Hub: https://hub.docker.com/r/laromicas/romvault/ Github: https://github.com/laromicas/docker-romvault.git Based on: https://github.com/jlesage/docker-baseimage-gui.git Based on Ubuntu to show text properly. Make sure to look at the complete documentation, available on Github ! Known Issues: - Accessing several items in the help menu crashes the application. - SAM-UI (former trrntzip) cannot be used really as it doesn't have any way to drag files. Edit 2024-0625: - Updated ROMVault to 3.7.2. Edit 2023-06-24: - Updated ROMVault to 3.6.1. Edit 2023-05-28: - Updated ROMVault to 3.6 WIP5 which fixes datvault issues. - Changed base to Ubuntu, it fixes text display. Edit 2023-05-05: - Fixed window management inside NoVNC, DatVault hangs the application. Post any questions or issues relating to this docker in this thread.
-
Passthrough USB Hardware goes completely unresponsive, have to reboot server
It happens with every usb port. I have tried all of them.
-
Passthrough USB Hardware goes completely unresponsive, have to reboot server
Hi, Did you solve the issue? I am having a similar problem with unraid. Aug 19 22:45:07 LakNAS root: plugin: running: anonymous Aug 19 22:45:07 LakNAS root: plugin: running: anonymous Aug 19 22:45:36 LakNAS nginx: 2022/08/19 22:45:36 [error] 5699#5699: *124209 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.1.100, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/2.0", host: "192.168.1.150", referrer: "https://192.168.1.150/Shares/Browse?dir=/mnt/user/logs" Aug 20 06:50:41 LakNAS kernel: xhci_hcd 0000:02:00.0: xHCI host controller not responding, assume dead Aug 20 06:50:41 LakNAS kernel: xhci_hcd 0000:02:00.0: HC died; cleaning up Aug 20 06:50:41 LakNAS kernel: usb 1-7: USB disconnect, device number 2 Aug 20 06:50:41 LakNAS kernel: usb 1-9: USB disconnect, device number 3 Aug 20 06:50:41 LakNAS kernel: usb 1-10: USB disconnect, device number 4 Aug 20 06:50:41 LakNAS kernel: FAT-fs (sda1): Directory bread(block 30546) failed Aug 20 06:50:41 LakNAS kernel: FAT-fs (sda1): Directory bread(block 30547) failed Aug 20 06:50:41 LakNAS kernel: FAT-fs (sda1): Directory bread(block 30548) failed Aug 20 06:50:41 LakNAS kernel: FAT-fs (sda1): Directory bread(block 30549) failed After some time of the server being up (several hours), I get to this error, and after this the server becomes unresponsive. I have to restart the server again and again... Do you know what can be happening?