tjb_altf4

turning on advanced view on docker (list) page and using the force update option is the easiest way to force the env to be refreshed when working with env files

I migrated mid last year, looking at my backups to piece together my upgrade path: I went from 7.4.162 to 8.0.24 (last tagged release) in lsio container from there I backed up and imported into unborn container running same tag then upgraded to 9.3.43 later upgraded to 9.5.21 where I current sit (still need to move to 10.x)

I believe eMMC support was added in 7.2.0, additionally more boot options are coming: https://www.youtube.com/watch?v=5_joxU7TNas

Wake me up for multi array

Jesus christ on a stick, they're asking for the current setting to be shown, not how to disarm a bomb.

Nvidia dropped support for Pascal series GPUs, but it should work on older drivers still (580 series). I would recommend posting in nvidia plugin thread if you continue to have issues: https://forums.unraid.net/topic/98978-plugin-nvidia-driver

your compose has this: ports: - 192.168.30.10:2283:2283but ports section should only have ports: ports: - 2283:2283I don't think ports are required when setting static IPs, but will be ignored and can be a useful reference.

This is a docker engine issue and doesn't work quite the same as a normal dhcp service. The work around is change the docker network dhcp pool so that it excludes a range that you will be assigning static IPs to. Also note that within a specific docker custom network, other containers IPs in that network are resolvable by container name, so if your tunnelling app is in same network as "whoops", you can use the container name instead of relying on a static IP.

if the containers are saving logs separately, you need to manage per service in the application config/settings like you would do for bare metal installs on any other system. However, the standard design pattern for docker is that logs get redirected to STDOUT/STDERR (if not already sent there), and docker manages these logs, which are available via "docker logs SOME-CONTAINER-NAME"

You can enable and configure log rotation for docker (all containers) in Settings > Docker. You'll need to stop the Docker service if its running, and toggle advanced mode to see the settings.

Binding to VFIO is a method to hide it from the host so you can passthrough the device for use in VMs. If you intend to use it for Unraid, you need to undo that change and it should appear in network settings after a restart.

This is a great change, but I hope some thought is being put in for user friendly disaster recovery... maybe the ability to use the your old usb as a recovery device (and backup target), and/or a mode where you could pull down unraid connect backups.

The psu will have a common 12V rail design, the backplane you are hooking it up to will (likely) also have a common 12V rail... you're overthinking it. I'm not sure what evidence your statement "It seems that the peripheral PSU ports can't hand the 12v amps" is based on. IMHO your considerations should be: will the PSU handle the overall 12V and 5V load (and 12V surge peak at start-up for HDD motors)? will the cables from PSU to backplane have sufficient headroom for continuous use and any transient usage peaks.

its the same image and the template is from the same author, I'm guessing at some point the template was renamed, but the old one stuck around for legacy reasons. in summary, no advantage in trying to use the other template

ask limetech, I'm just showing that the UI behaviour has changed... may have been an intentional design decision for consistency, or might have been an oversight

always been there, even on black & white themes but ahs gone on recent versions (since we went "responsive layout" I'd imagine)

Once your network (outside of Unraid) is setup for vlans, you can add them to the network settings in Unraid per NIC, then you add them to network setting on the Docker service settings page. The network config will change depending on your network equipment, which needs to be vlan capable, but for the Unraid side its as below. Taking an example vlan of my "servers" on Network settings page, which creates the br1.20 (interface-or-bridge-name dot vlan-id) : note that I've masked some elements of my network config Docker service settings page (service needs to be stopped to change), vlan configured in settings this is how a container is configured in template, if you don't specify fixed address it uses your configured DHCP pool from Dockers page (docker doesn't use router DHCP) and subsequent container instance:

For me personally, everything has individual IPs per container using custom networks via my configured vlans (out of the box unraid configs). I couldn't imagine going back to the nightmare of managing port mapping conflicts, host shim network hacks, and lack of container name resolution... not to mention the overhead of an extra NAT layer.

its not bad practice, but it is more of an advanced setup with some caveats which new users struggle with...so users are generally steered away from it.

this method was broken in recent releases to patch up tailscale vulnerabilities.

Using CA to run a 2nd app has always been difficult, and for most users this is the only way they know how to add containers... and don't know of the Unraid OS functionality for creating containers.. The best way to add additional containers is via Unraid's add container button on the docker page, and select the template for the container you already added (by CA). Make sure you change the container name, ports and paths so they are different to the one already running.

Seems to be an Unraid problem, binhex has a fully functional container... how is Binhex supposed to anticipate what random scripts get injected by the Unraid OS?

It's not a Java viewer, that's for much old boards... it'll be HTML5 and not have any prerequisites for you to use

sounds like you interrupted the migration. you can try and restore your old library and try migration again (automatic) as per the release notes: https://jellyfin.org/posts/jellyfin-release-10.11.0/

This is probably a UX issue, can't blame you to be honest. Next is the name of the branch that has Unraid prerelease builds, it's not a progression button. To upgrade you (unintuitively) have to select "View Changelog" for the stable version so that you can get to the upgrade button for that version.