On 7/9/2026 at 4:40 AM, Pete0 said:

Updated from 7.3.1. to 7.3.2. without issues.

Only one minor point that I have seen just now: a custom icon png file is not displayed anymore for a docker container, which worked before the update.

The file is still present.

All is well with the update and I am running 7.3.2 now, with seemingly no issues other than my custom Docker icons not displaying either. I'm a little sad 😥 I drew them up myself.

Edited July 13Jul 13 by craigr

I did also try to "Force Update" the Dockers to see if the icons would populate, but they did not. The path leads to a folder in my appdata location. I tried uploading them to my web host and using a URL pointing to them. Nothing seems to work.

2 hours ago, craigr said:

with seemingly no issues other than my custom Docker icons not displaying either.

Using local paths is not supported there, you are supposed to enter a URL, and the field mentions, previous support for local paths was accidental I believe, and it didn't always work.

I moved my icons onto GitHub but I imagine most image hosting services would also work.

9 hours ago, JorgeB said:

Using local paths is not supported there, you are supposed to enter a URL, and the field mentions, previous support for local paths was accidental I believe, and it didn't always work.

Works just fine
file:///mnt/cache/appdata/_icons/custom-icon.png

note 3x slash after file:, not just 2x
file:///

30 minutes ago, btTeddy said:

Works just fine
file:///mnt/cache/appdata/_icons/custom-icon.png

note 3x slash after file:, not just 2x
file:///

Excellent thank you. I did not have "file:" at all before, let alone three forward slashes. Works now.

Used to work fine without "file:///" for me.

Yay! 😀

For what is this "file:///" ?

In my case, it doesnt work...

Just the path "/mnt/cache/appdata/icons/plex.png" and all is fine.

Can someone explain this?

Edited July 14Jul 14 by Zonediver

11 minutes ago, Zonediver said:

For what is this "file:///" ?

In my case, it doesnt work...

Just the path "/mnt/cache/appdata/icons/plex.png" and all is fine.

Can someone explain this?

I would suspect that it is browser related. What works in one browser does not work in another browser...

1 hour ago, Frank1940 said:

I would suspect that it is browser related. What works in one browser does not work in another browser...

Nothing to do with the browser. Works ion both Chrome and Firefox

1 hour ago, Zonediver said:

For what is this "file:///" ?

In my case, it doesnt work...

Just the path "/mnt/cache/appdata/icons/plex.png" and all is fine.

Can someone explain this?

Are you using this for file folder plugin by any chance?

containers need
file:///mnt/cache/appdata/_icons/icon.png
while folderview plugin
/mnt/cache/appdata/_icons/icon.png

3 hours ago, btTeddy said:

Nothing to do with the browser. Works ion both Chrome and Firefox

Are you using this for file folder plugin by any chance?

containers need
file:///mnt/cache/appdata/_icons/icon.png
while folderview plugin
/mnt/cache/appdata/_icons/icon.png

?

8 hours ago, Zonediver said:

For what is this "file:///" ?

That is how one refers to a local file in URL format.

Whether local files are allowed can I believe sometimes depend on security settings in the browser.

Upgraded both servers and no problems. Well, one very minor one, I had to reboot a Windows client after I try to access a server too quickly after it came back online and something went wrong in the login client-server handshaking.

Updated to 7.3.2 and had the same issue as with the last update where some docker containers didn't show up and needed to be deleted with docker rm and re-created. Not sure why this happened again with other containers than before.

Upgrade went smooth but am having some issues with frigate since updating.
Frigate records to a zfs mirrored pool of 2tb sata SSDs.
Drives seem ok. But having issues viewing recordings etc...

Anyone else got issues?

Frigate docker container with usb coral is working for me without any problems. (but no ZFS, only BTRFS)

reboot, restart might help.

Edited July 15Jul 15 by NoRaid99

My unRAID setups upgraded to 7.3.2 without any issues.

I recently purchased a couple of the Patriot P300, 128GB, drives to use for the unRAID OS. And move from a USB stick to an NVMe drive. In the two Terramaster F6-424 boxes I setup recently (unRAID 8 and 9). Hopefully, I don't have any issues.

Edited July 15Jul 15 by aaronwt

I have just updated to 7.3.2 and all seems good, I can access Frigate recordings.

Is anyone using the net.unraid.docker.icon label with Docker Compose? That's been broken for me since the update. In the past, I used local paths like:

- net.unraid.docker.icon=/mnt/user/appdata/__containers/_icons/flexget.png

and I understand that broke for everyone. However, this doesn't work either:

- net.unraid.docker.icon=file:///mnt/user/appdata/__containers/_icons/flexget.png

I finally moved the file to a publicly available HTTPS directory, but still no luck:

- net.unraid.docker.icon=https://example.com/_icons/flexget.png

All of these examples just show generic question marks next to my containers. Is it just me?

9 minutes ago, flammable said:

Is anyone using the net.unraid.docker.icon label with Docker Compose? That's been broken for me since the update. In the past, I used local paths like:

- net.unraid.docker.icon=/mnt/user/appdata/__containers/_icons/flexget.png

and I understand that broke for everyone. However, this doesn't work either:

- net.unraid.docker.icon=file:///mnt/user/appdata/__containers/_icons/flexget.png

I finally moved the file to a publicly available HTTPS directory, but still no luck:

- net.unraid.docker.icon=https://example.com/_icons/flexget.png

All of these examples just show generic question marks next to my containers. Is it just me?

On 7/13/2026 at 1:34 PM, btTeddy said:

Works just fine
file:///mnt/cache/appdata/_icons/custom-icon.png

note 3x slash after file:, not just 2x
file:///

@wgstarks Right, I tried that (it's in my post). It doesn't work for me on Unraid 7.3.2, at least with Docker Compose and that label.

I also have the same problem.
I am deploying containers via Portainer, and 2 of them use the same icon. One showing, the other not.

# Name
name: cloudflare
services:
# CloudflareD Tunnel
  cloudflaretunnel:
    image: cloudflare/cloudflared:latest
    container_name: cloudflare_tunnel
    hostname: cloudflare_tunnel
    environment:
      - TUNNEL_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - PUID=99
      - PGID=100
      - TZ=Australia/Sydney
    labels:
      - net.unraid.docker.managed=dockerman
      - net.unraid.docker.icon=/mnt/user/appdata/icons/cloudflare.png
    command: tunnel --no-autoupdate run
    networks:
      - frontend
    restart: always
# CloudFlare DDNS by Favonia
# https://github.com/favonia/cloudflare-ddns
  cloudflare_ddns:
    container_name: cloudflare_ddns
    hostname: cloudflare_ddns
    image: favonia/cloudflare-ddns:latest
    environment:
      - PUID=99
      - PGID=100
      - TZ=Australia/Sydney
      - CLOUDFLARE_API_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - DOMAINS=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - PROXIED=false
      - IP6_PROVIDER=none
      - SHOUTRRR=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    labels:
      - net.unraid.docker.managed=dockerman
      - net.unraid.docker.icon=/mnt/user/appdata/icons/cloudflare.png
    networks:
      - frontend
    restart: always
# Networks
networks:
  frontend:
    external: true

So weird.

I tried a web link like `https://raw.githubusercontent.com/prophetse7en/cloudflare-tunnel/main/cloudflare-icon.png`, same result
I tried the same PNG file from another location, without any luck.

I tried to use `net.unraid.docker.icon="file:///mnt/cache/appdata/_icons/custom-icon.png"`, still no luck.

Well, after scratching my head for a bit and digging, I have found a solution 😊

If you are using Docker Compose with labels, then this will fix yours.

So, pay attention to your container name, and make sure its icon exists in /var/local/emhttp/plugins/dynamix.docker.manager/images
with this format contianrname-icon.png Don't forget -icon In the name 😊








The thing I didn't try is a restart, so I am not sure if it stays after restarting the server.

That location is only in RAM so will not survive a reboot. The image needs to be stored on the boot drive, so I expect that 'config/plugins/dockerMan/images' location on the boot drive is where you need to store them to survive a reboot. I do not use Compose so cannot test it. It is possible you might need to run a script to move them into position during the boot sequence, but the User Scripts plugin would make this easy.

16 hours ago, itimpi said:

That location is only in RAM so will not survive a reboot. The image needs to be stored on the boot drive, so I expect that 'config/plugins/dockerMan/images' location on the boot drive is where you need to store them to survive a reboot. I do not use Compose so cannot test it. It is possible you might need to run a script to move them into position during the boot sequence, but the User Scripts plugin would make this easy.

Yeah, that is what I thought. So, a temp Band-Aid to have a script to copy them over during startup.
Easy peasy :)

Wondering why some of them exist there?
That means something copied them over, but not all?!