[BUG] Dockerfile not matching / building latest upstream stable release (10.2.105)

[MajorP93]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When running your logic / matcher for retrieving latest available "Unifi Network Application" it returns release 10.1.

Version 10.2 has been released already: https://community.ui.com/releases/UniFi-Network-Application-10-2-105/cf38dace-ce91-4e4a-8ab7-a1d2db30aa55

Since the matching logic in Dockerfile does not "find" the new release it does not get built.

Does the logic in Dockerfile need to be updated in order to find / retrieve the new version?

Would love to be able to update my instance.

Thanks a lot for maintaining this Docker image. Much appreciated.

Best regards

Expected Behavior

Latest stable release of Unifi Network Application being built/used by Dockerfile.

Steps To Reproduce

Try to build this image locally. It will not find / build latest available Unifi network application release.

Environment

- OS:latest Raspbian on Raspberry Pi 5
- How docker service was installed: docker convenience script

CPU architecture

arm64

Docker creation

---
services:
  unifi-network-application:
    image: linuxserver/unifi-network-application:latest
    container_name: unifi-network-application
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - MONGO_USER=unifi
      - MONGO_PASS=${MONGO_PASS}
      - MONGO_HOST=unifi-db
      - MONGO_PORT=27017
      - MONGO_DBNAME=unifi
      - MONGO_AUTHSOURCE=admin
    volumes:
      - ./app-data:/config
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
      - 1900:1900/udp #optional
      - 8843:8843 #optional
      - 8880:8880 #optional
      - 6789:6789 #optional
      - 5514:5514/udp #optional
    restart: unless-stopped
  unifi-db:
    image: mongo:7.0
    container_name: unifi-db
    environment:
      - MONGO_INITDB_ROOT_USERNAME=root
      - MONGO_INITDB_ROOT_PASSWORD=${MONGO_INITDB_ROOT_PASSWORD}
      - MONGO_USER=unifi
      - MONGO_PASS=${MONGO_PASS}
      - MONGO_DBNAME=unifi
      - MONGO_AUTHSOURCE=admin
    volumes:
      - ./mongodb-data:/data/db
      - ./init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro
    restart: unless-stopped

Container logs

user@linbox:~> curl -sX GET "https://fw-update.ubnt.com/api/firmware-latest?filter=eq~~product~~unifi-controller&filter=eq~~platform~~unix&filter=eq~~channel~~release" \
                                                | jq -r '._embedded.firmware[].version' \
                                                | awk -F '+' '{print $1}' \
                                                | tr -d 'v'
10.1.89

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

As with every time we've been asked this in previous issue's, the container gets upgraded once unifi push an update to their apt repo then our systems will detect the update and build the new version.

[MajorP93]

@j0nnymoe Thanks for clarifying. I did not know that. That explains why Dockerfile did not pick up the new version.
Now that you mentioned this I found the info in a closed issue.
Sorry for duplicate question.

[j0nnymoe]

All good, I've just re-pinned the issue so users are aware :)

[MajorP93]

@j0nnymoe Hmmm I checked the pinned issue. The old method of checking version number (looking at https://dl.ui.com/unifi/debian/dists/stable/ubiquiti/binary-amd64/Packages.gz) that is explained there indicates that version 10.2.105-33556-1 has already been pushed to apt repository by Unifi.

I saw that you switched to another method for checking / downloading the package which relies on their API.
I am not sure if that method is still working fine going forward?

[MajorP93]

user@linbox:~> curl -sX GET https://dl.ui.com/unifi/debian/dists/stable/ubiquiti/binary-amd64/Packages.gz | gunzip | grep -A 7 -m 1 'Package: unifi' | awk -F ': ' '/Version/{print $2;exit}' | awk -F '-' '{print $1}'
10.2.105

user@linbox:~> curl -sX GET 'https://fw-update.ubnt.com/api/firmware-latest?filter=eq~~product~~unifi-controller&filter=eq~~platform~~unix&filter=eq~~channel~~release' | jq -r '._embedded.firmware[].version' | awk -F '+' '{print $1}'
v10.1.89

[MajorP93]

After reverting 5e1211d I was able to build this image for upstream release 10.2.105.

I consider this issue worth re-opening.

[j0nnymoe]

I've raised this internally, will see what other people say.

Also worth noting that Unifi do plan to eventually drop support for this in favour of their UnifiOS product. So we can't guarantee how much longer this will continue to be built for.

https://info.linuxserver.io/issues/2026-02-22-unifi-network-application/

[MajorP93]

@j0nnymoe Thanks for the hint.

The post you linked states "We will support our Unifi Network Application image for as long as Ubiquiti continue to make the install packages available to download".

That seems to be aligned with the goal that you previously explained to release docker images for all releases that get pushed to the upstream apt repository for Network Application.

The underlying mechanism seems to not work currently which is why I think it would make sense to re-open this issue and investigate if their API can still be used to reliably determine latest available release in the upstream APT repository.