Community Apps

Locate your drives and assign them to a graphical tray map to get full overview of installed hard drives in your system.

Locate your drives and assign them to a graphical tray map to get full overview of installed hard drives in your system. NB! This is the developer edition of the plugin, use with CAUTION and OWN RISK!

This container will fully install a RetroNAS VM into the VMs tab of your server. It downloads an a vDisk image, verifies it with a checksum before creating a vm template and installing the VM for you. What you choose in the container varaibles will reflect to the vm. For most people these dont need to be changed from the defaults. If you need to change the locations in the container this is what each will do. VM Share on Server: This should be set to your VM share - default on Unraid is /mnt/user/domains - the vm will be installed here RetroNAS data share This should point to a share you want RetronNAS to use. All your roms etc will be here. Best have an empty share and move what you need there later. default is retronas. The container will connect the VM using virtiofs to this share. So the share doent have to be "exported" by Unraid for retroNAS to use it (more secure) Name to call VM: Easy -- The name you want the VM to be called default id RetroNAS but you can change it The container then will do the rest. It will create an xml file for the vm based on the above and install the vm straight into the server. So once run goto the VMs tab and you will see it there. Start it up and confiure retronas in vnc window and configure (see my video how) default username and password is retronas (yes you can change them later! ) After logging in type retronas to configure your RetroNAS server. Have fun :) The container doesnt need to be kept running. It is just an install tool. The container has no webUI so to see what its doing view the container log. ** This container cant translate the location of an unassigned disk across to the vm template. So all locations choosen must be on the array or pool device.

Telegraf gathers metrics from your system and sends them to an InfluxDB server for storage. From InfluxDB you would typically use something like Grafana to plot the data. Both Grafana and Influxdb are available through Community Apps This version of telegraf requires you to manually place a config file at /mnt/user/appdata/telegraf/telegraf.conf The container will not start without it. The default telegraf.conf file can be extracted from telegraf by running this command before you launch telegraf docker run --rm telegraf telegraf config > /mnt/cache/appdata/telegraf/telegraf.conf Configuration Container Volumes: /var/run/docker.sock Read Only. Location of your docker socket. /var/run/utmp Read Only. Location of your utmp file. /run/udev Read Only. Allows you to identify devices based on their properties, like vendor ID and device ID /rootfs Read Only. To be mapped to the root of the host file system. This is so the disk usage reported will be that of the host system. /rootfs/etc Read Only. To be mapped to the etc of the host file system. This is so the disk usage reported will be that of the host system. /rootfs/proc Read Only. To be mapped to the proc of the host file system. This is so the disk usage reported will be that of the host system. /rootfs/sys Read Only. To be mapped to the sys of the host file system. This is so the disk usage reported will be that of the host system. Environment Variables: HOST_MOUNT_PREFIX Name of container volume mapping of the root file system. HOST_ETC Name of the etc volume mapping of the root file system. HOST_PROC Name of the proc volume mapping of the root file system. HOST_SYS Name of the sys volume mapping of the root file sytem.

This container will install a fully updated Windows 98SE virtual machine (VM) into the VMs tab of your server. The container variables that you select will apply to the VM, and for most users, the default settings are sufficient and do not require modification. However, if you need to change the locations within the container, here is a brief explanation of what each location does. The "VM Share on Server" setting should be configured to reflect the location of your VM share. By default, the VM share on Unraid is located at /mnt/user/domains. The "Name to call VM" setting is straightforward. It allows you to choose a custom name for your vm. The default name is "Windows 98" but you have the option to change it to any desired name. Windows 98 type WIN98-KernelEX This allows Win98 to run some Win2000 and XP software WIN98-Normal Normal vanilla install After configuring the container variables as described above, the container will take care of the rest. It will create an XML file for the Win 98 virtual machine based on your selections and install the VM directly onto the server. Once the container has been run, you can go to the VMs tab and locate the installed VM. It is important to note that the container does not need to be kept running after installation. It is simply a tool for installation purposes and does not have a web user interface (UI). To monitor the container's progress, you can view the container log. ** This container cant translate the location of an unassigned disk across to the vm template. So all locations choosen must be on the array or pool device.