primeval_god

What version of unRAID are you running?

I assign different IP addresses to each interface and isolate one from the webui and use it for docker containers.

https://docs.docker.com/compose/networking/#use-a-pre-existing-network or perhapse https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode

I have also never yet had a server die. I have had power supplies die, and disks, and a GPU once but never the motherboard, processor or ram. All those that i have had have survived long enough to be replaced as part of an upgrade. If i had a board die in the 5+ year timeframe i would likely not waste time on finding a compatible replacement, I would just swap out all the core components for something newer.

From the compose page select the gear and then edit stack. Choose the button that says UI Labels and on the lines that say Shell enter the shell that is available in your containers (typically bash or sh).

For the console button to work you have to specify the proper shell in the UI Labels.

Check the settings page.

You can also enable compression on a subvolume, with more options than chattr but less that with mount. Anything written under the subvolume, including other subvolumes are compressed as well.

Doubtful that there would be any speed difference.

I have not done it myself but nothing in the compose plugin should break the functionality. You are talking about this correct https://docs.docker.com/compose/environment-variables/#the-env_file-configuration-option?

You can use the 'env_file' option in your compose file to specify an env file anywhere you like. The compose manager ui however will only allow you to edit the env file in stack directory.

Variants on this theme have been requested before but i could not find anything recent or similar. To compile and package plugins for unRAID i use a github action that builds the package in a slackware docker container. I have been using vbatts/slackware and more recently aclemons/slackware images and trying to match them as closely as i can to the version of slackware (and packages) unRAID is based on. It would be really cool if limetech could maintain their own unraid base environment image that contained the exact version and packages used in each version of unRAID (including all the basic dev packages that get stripped out). Obviously it would be only the base OS without things like the webui, array driver, startup scripts/customizations, etc, so it would only really be useful for plugin development. Still i think it would be very helpful plugin developers both existing and aspiring.

This would be a feature request for the unRAID webui rather than this plugin. Currently in dockerman only the icon, webui link, and console selection can be specified by docker label. At this time no further integration with the Dockerman update functionality is planned sorry.

The primary draw of unRAID is parity without striping. One way of thinking of unRAID is kind of like a JBOD with a parity disk (or two). Each disk (except parity) has its own complete filesystem, you can even be a mix of BTRFS and XFS disks. Parity is calculated in real-time over the raw disks and stored on dedicated parity disks. The user share system provides a unified (merged) view of the entire array and provides rules to control which disks files are written to. Individual files cannot span disks. With unRAID you can mix and match drive sizes with the only rule that the parity disk(s) must be as large or larger than the largest data disk in the array. Adding additional disks or replacing disks with large ones is easy (though you do typically have to stop the array for a short time to do so). Downsizing is possible but a bit more of a hassle (though not as much as other systems). At this time only a single unRAID array can be (and must be) created per server. Additional pools can be created using BTRFS (with BTRFS stripe or mirror modes), these are typically used for a form of new file write cache or to store application data.

First off those messages are about the "/media" mount which is where urBackup is going to store your backup data. Despite being labeled as errors those are just urBackup testing whether or not it can use btrfs or zfs specific features in the backup location, if it cant then they are not errors. If you are expecting it to make use of the BTRFS filesystem then the container needs to be run as privileged. If you do have the /media location on your cache drive you will need to make it cache only. You can read back in this topic but i dont think unRAIDs mover necessarily plays nice with urbackups storage architecture, it certainly wont with the BTRFS specific features. If you point /media at the array and intend to use the BTRFS specific features you will need to point it directly at a BTRFS formatted disk share.

As a very happy unRAID user (not affiliated with the company in any way) who also enjoys a good rant now and again please allow me a bit of a rebuttal. unRAID is a home NAS operating system. It is a consumer oriented product not an enterprise solution. Please stop expecting enterprise features from consumer products. Zero downtime and 24/7 support are enterprise features that one should expect to pay large amounts of money for on an ongoing basis. Limetech is a very small company with a somewhat niche product, the amount of support and ongoing improvements they provide for your onetime license fee is frankly astounding. If you have logs being written to your flash drive you are doing something wrong. The flashdrive is meant to be a fairly static storage area for the os image and a few small configuration files. unRAID runs from RAM and writes to the flash drive on a properly configured system should be few and far between. The use of fat32 should not be an issue because the entire os should stay small enough to run completely out of RAM. unRAID is not the only NAS device out there that boots from a flash drive. Terramaster for one i believe has their home NAS appliances booting from an internal usb flash drive. And just to reiterate my opinion on this one, unRAID is in fact a home NAS appliance not a generic linux os or an enterprise solution. My sub $20 flash drive has been going strong for 5+ years. I know that finding good flash drives is harder these days but many people still are. One thing i would like to see is either a community or limetech led effort to identify a good brand / source of flash drives and then a community buy or better yet limetech (or someone) buying in bulk and reselling said drives to the community (if the price is right no warranty necessary). The above said, i am sorry to hear or your troubles and you really should look into stopping whatever is logging to your flash drive. I would bet it is a big source of your troubles. I do apologize for the counter rant as we generally try to cultivate a supportive rather than standoffish community. Your opinions and feedback are welcome even if some of us disagree.

Just create a file in your appdata folder on the host named "backupfolder" that contains the text "/media" (no quotes). Then in the dockerman template add a new path from the backup folder file on the host to "/etc/urbackup/backupfolder" in the container. Make sure you specify the filename in the path and not just the folder it's in. I marked mine as read only in the template. And that's it.

Has anyone managed to setup internet urBackup clients through a reverse proxy (specifically traefik but i dont think the proxy is the issue) using websockets and basic auth? I have been following the relatively sparse information from the urbackup site and forums but I find myself stuck. Nearest i can tell despite embedding the basic auth credentials in the url the client doesnt send them with its websocket connect request. Anyone encountered something similar?

This does in fact need to be a text file named "backupfolder" that has the path of the backup folder in it. The thing that may be wrong is the location. From what i understand it needs to be "/etc/urbackup/backupfolder". Bind mounting a file containing /media to that location fixed the Backup Folder not set messages for me. I cant speak to the others.

I would be somewhat surprised if ZFS were introduced as an FS option for the main array. More likely zfs will be an alternative to BTRFS for multidisk pools.

I was unaware that environmental variables were an option...

Anyone else having issue with my.jdownloader.org credentials not being saved across container restart?

Icons are set with a container label net.unraid.docker.icon point to the address of an appropriately sized png image.

You would likely need to provide diagnostics for someone on the forum to provide help for your specific share layout. While I have no idea if it effects your layout or not one thing to keep in mind that trips up some people unfamiliar with unRAID is that cache drives are only for new files. Files that are already on the array will be modified in place and are never moved from disk to disk automatically. Applications that modify files in place can fill a disk beyond limits placed at the share level.

You kind of downplay the difference here but for me realtime parity protection is an important point. For my money I want my data protected the moment it hits my NAS, either by the unRAID array or by a mirrored cache pool. And while i do make use of cache pools, for many of my home usage scenarios writing directly to the array is plenty fast enough.