tjb_altf4

Should work out of the box without additional configuration on the Unraid side.
I'd be looking at the mikrotik's port configuration... noting that you are running tagged and untagged traffic on br2 which likely needs additional configuration.

Short answer, try 8095:80

Long answer, taken from docker docs:

Publishing ports
Publishing a port provides the ability to break through a little bit of networking isolation by setting up a forwarding rule. As an example, you can indicate that requests on your host’s port 8080 should be forwarded to the container’s port 80. Publishing ports happens during container creation using the -p (or --publish) flag with docker run. The syntax is:
docker run -d -p HOST_PORT:CONTAINER_PORT nginx HOST_PORT: The port number on your host machine where you want to receive traffic
CONTAINER_PORT: The port number within the container that's listening for connections
For example, to publish the container's port 80 to host port 8080:
docker run -d -p 8080:80 nginx Now, any traffic sent to port 8080 on your host machine will be forwarded to port 80 within the container.

https://docs.docker.com/get-started/docker-concepts/running-containers/publishing-ports/

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

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.

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.

Docker only uses its internal DHCP, if you want a specific IP for a container, you have to set it in the docker container template.
Pfsense (or any other router) cannot assign an IP to a docker container.
You are simply reserving the IP for the container in pfsense, so that pfsense doesn't hand out that address to another computer, which could happen when container is stopped.

On the Docker page, at the bottom there is a 'Container Size' button, this will retrieve metrics for usage.
Container is the application layers itself.
Writeable is any volumes, or data being written in unmapped space, and is where to look for problems with individual containers.
Log shouldn't be too large, if there are any outliers here you might need to ensure you have log rotation enabled in Docker settings.

br0.20 has an invalid dhcp pool mask, most likely should be 10.10.20.128/25
Recent releases of Unraid have become more strict around correctness of docker network settings, which is why it might have worked in the past.

try this format instead:
--gpus device=GPU-fd7c39b4-1d44-8d62-02c0-0d559985fa47

more info here: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html

Its a plugin you added to your install called GUI Links, go to plugins and select remove for that plugin
 
 

Answered over on Discord, notification is from Dell's idrac (out of band management), unrelated to Unraid.
OP mentioned they had sold their Dell server long ago and wasn't reset to default, most likely left email creds in notifications and new owner started setting up alerts.

This is all you need to do, but you need to restart... or possibly force update (rebuild) the container for the envs to stick.





note: I've explicitly stated /mnt/cache, but /mnt/user is fine.

Sounds like nzget is being a resource hog and starving the system, try restricting cpu through pinning resources (avoid first 2 cores if possible).

example:


note: advanced view must be toggled to see this option in docker template

Unleased to Lifetime upgrade is USD$149


Info can be found here: https://unraid.net/pricing

9400-16i is capable of SAS3 (12G) speeds.
Each SAS port carries 4x SAS lanes, your HBA has 4 ports (16 lanes total).
You only have 4x SSDs, so with only that 1 port, even with a workload to max them out, the HBA would still not be a bottleneck.

Docker doesn't look for an env by default, you need to specify that it needs to read one.
 
Turn on advanced view in template, and look for "Extra Parameters", add this to that field, adjusting for the actual path to the env 🙂
 
--env-file=/mnt/user/appdata/homepage/.env
 
No special permissions required
 

You're using the AMD GPU specific image (rocm)

To expand and answer your question more directly, you'll want the convert to raid0 mode to combine storage.
You'll get a performance improvement, but be aware if one disk fails, data on both will be gone.

Most of your "lost" capacity is actually from comparing different measurement units (TB vs TiB)
To start with your unformatted space from 7 disks gets you about 51TiB (56TB)
 
If you go to the SHARES tab, you can press the "Compute..." button to see where storage is being used and what is free.

You mention a few times you prefer a lifetime licence option... Unraid still has a lifetime licence
Also, If you don't chose a lifetime licence option, nothing stops working in future when your sub expires, other than availability of Unraid OS updates.

There is no GUI interface for creating or deleting docker networks (I'm assuming this is what you are referring to).
Instead you need to go into the CLI and type: docker network rm <my-network>
Where <my-network> is the name of your network to be removed, this can also be stacked if you like e.g. docker network rm <my-network1> <my-network2> <my-network3>
 
If you don't know what networks you have, type docker network ls
The Unraid default docker networks are br0 (and br1, brx etc for each interface), bridge, host, none and wg0
 
Note that any containers still configured to use that network will fail to start, but you can adjust this in the docker settings.
If a containers is still running and using one of these networks the command will likely fail to remove it.
 
Example:
root@fortytwo:~# docker network ls NETWORK ID NAME DRIVER SCOPE f65acde003bd br0 ipvlan local 8ba0d062c51e br1 ipvlan local b410faa93e33 bridge bridge local f14e96c2b3e7 go-spacemesh_spacemesh bridge local 5974bf6e7616 host host local 6ef32c3f7c35 none null local d51a9a1ed7b1 pihole bridge local 6c61ba876986 proxynet bridge local 1fd749e6cfc9 wg0 bridge local root@fortytwo:~# docker network rm go-spacemesh_spacemesh go-spacemesh_spacemesh root@fortytwo:~# docker network ls NETWORK ID NAME DRIVER SCOPE f65acde003bd br0 ipvlan local 8ba0d062c51e br1 ipvlan local b410faa93e33 bridge bridge local 5974bf6e7616 host host local 6ef32c3f7c35 none null local d51a9a1ed7b1 pihole bridge local 6c61ba876986 proxynet bridge local 1fd749e6cfc9 wg0 bridge local root@fortytwo:~#  

Macvlan docker network type is the likely cause of your kernel panics, this is a known issue and such a common problem in recent releases that it is no longer a default setting.
The fix in this case is to change docker network type from macvlan to ipvlan, which involves stopping the docker service:
go to SETTINGS > DOCKER with advanced view toggled (top right), set Enable Docker: No, then set Docker custom network type: ipvlan Once complete:
set Enable Docker: Yes to restart docker service. Report back with fresh diagnostics if kernel panics continue.

Once you have created a pool with at least 4 disks (btrfs), you can convert to raid10 using balance option under that pool's disk settings (click on first disk in pool from Unraid GUI > MAIN).

User Scripts plugin is the easiest way to work with scripting + cron in unraid, it also adds addition events for start/stop of array.
 

The docker folder plugin works with VMs also, which can achieve this effect.