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.

Edited July 23, 20241 yr by laromicas
Anouncing updates

Thank you for turning ROMVault into a unraid docker app.

 

DATVault side of the application seems to be very broken too. Sometimes it gets stuck trying to load, text is not showing in the list and I also cannot exit the DATVault popup screen.

Wow this is fantastic to see someone made a docker container for RomVault.

You may want to join the RomVault discord as well for issues with Linux or any other general questions about app usage. Although RV was not specifically created for Linux, many users do use it in various Linux VMs.

On 3/31/2023 at 9:11 PM, foldedpaper said:

Thank you for turning ROMVault into a unraid docker app.

 

DATVault side of the application seems to be very broken too. Sometimes it gets stuck trying to load, text is not showing in the list and I also cannot exit the DATVault popup screen.

Can confirm DATVault UI doesn't really work. I was able to copy old DATVault files from my windows installation of ROMVault to my server and the docker does read it properly and I can auto update the DATs.

 

So the two things that would be nice to fix are proper handling of pop-up windows (I think Binhex Krusader uses NoVNC which seems to handle that well) and fix the text in the DATVault window. Maybe using NoVNC would fix the text at the same time.

On 4/8/2023 at 8:25 PM, ralphpotato said:

Can confirm DATVault UI doesn't really work. I was able to copy old DATVault files from my windows installation of ROMVault to my server and the docker does read it properly and I can auto update the DATs.

 

So the two things that would be nice to fix are proper handling of pop-up windows (I think Binhex Krusader uses NoVNC which seems to handle that well) and fix the text in the DATVault window. Maybe using NoVNC would fix the text at the same time.

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.

FYI GordonJ just released 3.6.0 which should fix several linux-specific issues, especially with DatVault.

Getting a Permissions issue:

 

Quote

[openbox     ] Openbox-Message: 10:30:00.041: Unable to make directory '/config/xdg/cache/openbox': Permission denied
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[openbox     ] Fontconfig error: No writable cache directories
[supervisor  ] starting service 'app'...
[app         ] + HOME=/config
[app         ] + export HOME
[app         ] + cd /opt/romvault/
[app         ] + ls
[app         ] + grep -i ROMVault
[app         ] + grep -iv Cmd
[app         ] + RV_EXE=ROMVault36.exe
[app         ] + cd /config
[app         ] + ln -fs /opt/romvault/ROMVault36.exe /config/ROMVault36.exe
[app         ] ln: failed to create symbolic link '/config/ROMVault36.exe': Permission denied
[app         ] + true
[app         ] + ln -fs /opt/romvault/RomVaultCmd /config/RomVaultCmd
[app         ] ln: failed to create symbolic link '/config/RomVaultCmd': Permission denied
[app         ] + true
[app         ] + ln -fs /opt/romvault/chdman.exe /config/chdman.exe
[app         ] ln: failed to create symbolic link '/config/chdman.exe': Permission denied
[app         ] + true
[app         ] + rm -Rf /config/.config/.mono
[app         ] + mono /config/ROMVault36.exe
[app         ] Cannot open assembly '/config/ROMVault36.exe': No such file or directory.
[logrotate   ] mkdir: cannot create directory '/config/xdg/state': Permission denied

Not sure where else to put these permissions at as I added both USER_ID and GROUP_ID as variables, gave them the proper numbers/id and then restarted the container with the same issue.

Edited July 25, 20232 yr by CyrixDX4

On 7/25/2023 at 9:39 AM, CyrixDX4 said:

Getting a Permissions issue:

Not sure where else to put these permissions at as I added both USER_ID and GROUP_ID as variables, gave them the proper numbers/id and then restarted the container with the same issue.

 

Please send me the xml of your config to try to replicate the error.

Edited July 31, 20232 yr by laromicas

A couple of things I've noticed

 

* If you right click a dat and click Open Directory the application crashes.

* If you click the link icon in DatVault that would normally bring up the website for the dat in question it crashes.

* While it is scanning or repairing the box that comes up doesn't auto scroll down and scrolling left and right does nothing.  You can resize it though using the corner revealing the rest of the columns.

 

I honestly don't expect the first two to be fixed but I thought to at least get it out there for others to be aware of.

Edited September 23, 20232 yr by shinji257
Add one more crash scenario.

On 7/31/2023 at 5:25 PM, laromicas said:

 

Please send me the xml of your config to try to replicate the error.

 

Having the same issues as above with permissions

 

[openbox     ] Openbox-Message: 11:56:10.796: Unable to make directory '/config/xdg/cache/openbox': Permission denied

 

my-ROMVault.xml

Works fine with :

chown -R nobody:users ROMVault/

After the first time container run

Edited November 16, 20232 yr by Gaiserik

Trying to run this on a server with a NAS attached as a rootshare. No matter what I do, even if i run it on the NAS when it goes to move the files from cache it "fails to move file" with an error and stops working. I cannot find any logfiles to see why it cannot move the files, all the files have the 0777 permissions so im at a loss as to why its failing. I have tried with both cache specific tosort folder and a "general' tosort folder both fail. it has no problem moving to the cache, only moving from.

On 7/25/2023 at 4:39 PM, CyrixDX4 said:

Getting a Permissions issue:

 

Not sure where else to put these permissions at as I added both USER_ID and GROUP_ID as variables, gave them the proper numbers/id and then restarted the container with the same issue.

I don't know if this is the correct way to fix it, but I changed the premissions on the "ROMVault" folder inside "/mnt/user/appdata".

It worked for me, hope it helps someone else to...

Hi,

 

thank you for the container. I am a new UNRAID User. So forgive me if I am asking something obvious.

But is there any way to get access to the "RomVault3cfg.xml".

 

It isn't in the "appdata\ROMVault" config folder. Normally it is beside the .exe and cache file.

There are some RomVault options, which aren't accessible through the gui.

I would like to test the new "zstd" compression.

 

Thank you very much.

 

Edit: Hold on. I have't noticed that I have to make some changes in the settings to generate the "RomVault3cfg.xml".

I think this I had now fixed my issues.^^

Edited January 10, 20242 yr by BearWolf
Found a solution on my own. No help needed anymore :)

Dang; This is so much faster than trying to manage ROMs via SMB.  Thank you for the hard work!

 

Now I have to decide if it's worth re-hashing my entire library to take advantage of it.

 

I may see if I can trick RV into using my existing RomVault3_2.Cache file, but I don't have much hope.

 

After some experimentation, I have some good and bad news.

 

Good news; this container is much faster than SMB/virtiofs when crawling shares, and scanning ROMs that have already been hashed.

 

Bad news; the performance of hashing / repairing new ROMs is significantly slower than a Windows VM. Especially CHD files.

 

It appears that while newer versions of CHDman are multi-threaded, the mono interpreter is less-so.

 

Good news; an existing .cache file can be successfully dropped into the appdata/ROMVault folder, and Launchbox will use it.

 

You can use a VM or more powerful machine to hash/build your library, initially, and drop the .cache file into the container for routine maintenance.

Edited March 4, 20242 yr by nmkaufman

On 2/29/2024 at 3:06 PM, nmkaufman said:

Dang; This is so much faster than trying to manage ROMs via SMB.  Thank you for the hard work!

 

Now I have to decide if it's worth re-hashing my entire library to take advantage of it.

 

I may see if I can trick RV into using my existing RomVault3_2.Cache file, but I don't have much hope.

 

After some experimentation, I have some good and bad news.

 

Good news; this container is much faster than SMB/virtiofs when crawling shares, and scanning ROMs that have already been hashed.

 

Bad news; the performance of hashing / repairing new ROMs is significantly slower than a Windows VM. Especially CHD files.

 

It appears that while newer versions of CHDman are multi-threaded, the mono interpreter is less-so.

 

Good news; an existing .cache file can be successfully dropped into the appdata/ROMVault folder, and Launchbox will use it.

 

You can use a VM or more powerful machine to hash/build your library, initially, and drop the .cache file into the container for routine maintenance.

Thank you for your testing. I will take into account this recommendations.

On 2/29/2024 at 9:06 PM, nmkaufman said:

Dang; This is so much faster than trying to manage ROMs via SMB.  Thank you for the hard work!

 

Now I have to decide if it's worth re-hashing my entire library to take advantage of it.

 

I may see if I can trick RV into using my existing RomVault3_2.Cache file, but I don't have much hope.

 

After some experimentation, I have some good and bad news.

 

Good news; this container is much faster than SMB/virtiofs when crawling shares, and scanning ROMs that have already been hashed.

 

Bad news; the performance of hashing / repairing new ROMs is significantly slower than a Windows VM. Especially CHD files.

 

It appears that while newer versions of CHDman are multi-threaded, the mono interpreter is less-so.

 

Good news; an existing .cache file can be successfully dropped into the appdata/ROMVault folder, and Launchbox will use it.

 

You can use a VM or more powerful machine to hash/build your library, initially, and drop the .cache file into the container for routine maintenance.

What are you talking about? This is your first post on this thread. Would you please let us all know what do you mean by your post? I dont get it.

How did you manage ROMs via SMB? I though thats a transfer/file protocol by microsoft, not a ROM Manager. And whats about you "bad" and "good" news? Do you mean these news by using the Romvault Docker? Also, your clue is to use a VM instead of this docker, right?

I installed the container but every time I start it stops immediately.

Edited October 17, 20241 yr by Yugi154

@laromicasI hope you still support this.

 

I have the following issues if you can help.

1) In container configuration, I changed the paths of datroot, romroot and tosort (to somewhere with more space not my cache disk). But the container again created all three folders in appdata/ROMVault! (although I deleted them before restarting container)

2) I need an extra path to see the rest of my array, so I added it in the container configuration to have /UNRAID to my /mnt/user. Yet, when I start the container, I only see "personal" (which I think is ROMVault's home directory) and three SAME NVMe devices. I have two NVMe devices, I don't have my data there (this is why I added /UNRAID) and also they show empty. How can I make the container actually mount /UNRAID?

 

3) I would LOVE if RomVault3cfg.xml was in some folder that is accessible to me even outside the container (maybe a copy somewhere that start and stop of container copy from and to?), so that it can be edited manually (I have SEVERAL folders etc. and I don't want to add them from the GUI but instead use my Windows RomVault3cfg.xml and edit the paths).
Possible?

 

 

I don't know if this is the correct way to fix it, but I changed the premissions on the "ROMVault" folder inside "/mnt/user/appdata".

It worked for me, hope it helps someone else to...

This worked for me. I couldn't even get RomVault to run for the first time after installing it, but I could see that it did create the directory inside appdata, so I just used the file manager built right into Unraid's webgui, and changed the permissions of the romvault volder to Nobody. Container started right up first try after changing the folder permissions.

Just more upto date instructions for those using this from scratch in 2026

It failed to work on first run with the permissions issue..

1. I did change the appdata folder permission:

chown -R nobody:users ROMVault/

2. I had to delete the DatRoot, RomRoot and ToSort folders from the appdata\RomValue folder as I had these configured to folders on my array but it still created them in appdata..

3. (new) I had to edit the template, 'show more settings' and set "Take Config Ownership" to 1

Now, I'm in the webui and its scanning my roms..