Wrong api-information (versions)

Help docker
1

Hi,
I think the api-Information (versions) is in some cases wrong (core_update).

core_update	false
web_update	false
FTL_update	false
core_current	"v5.16.1"
web_current	"v5.19"
FTL_current	"v5.22"
core_latest	"v5.16.2"
web_latest	"v5.19"
FTL_latest	"v5.22"
core_branch	"master"
web_branch	"master"
FTL_branch	"master"

Who can help?

Best regards
Jürgen

2

Which docker image are you using?

If you are using the previous image 2023.03.0, this is the expected output.
The current image is 2023.03.1.

api.php?versions on 2023.03.0:

{
  "core_update": false,
  "web_update": false,
  "FTL_update": false,
  "core_current": "v5.16.1",
  "web_current": "v5.19",
  "FTL_current": "v5.22",
  "core_latest": "v5.16.2",
  "web_latest": "v5.19",
  "FTL_latest": "v5.22",
  "core_branch": "master",
  "web_branch": "master",
  "FTL_branch": "master"
}

api.php?versions on 2023.03.1:

{
  "core_update": false,
  "web_update": false,
  "FTL_update": false,
  "core_current": "v5.16.2",
  "web_current": "v5.19",
  "FTL_current": "v5.22",
  "core_latest": "v5.16.2",
  "web_latest": "v5.19",
  "FTL_latest": "v5.22",
  "core_branch": "master",
  "web_branch": "master",
  "FTL_branch": "master"
}
3

I am using the image 2023.03.0 and the expected output for "core_update": was "true" because there ist a new version avalable (my understanding).

The standard-installation on a pi deliver this value ("true").

4

the expected output for "core_update": was "true" because there ist a new version avalable (my understanding).

Not inside containers.

Inside containers, the default behavior is to only show updates for the image (as you can see on the web interface footer). Individual component versions will never show "update: true" inside containers.

5

What is the reason? The docker-installation has no separate value for a new version. Is it possible that the "api" delivers the same values in a docker-installation or an additional value for a new docker-version?

6

Checking the repo makes no sense for a Pi-hole container.

A dockered Pi-hole is not to be updated via pihole -up, but rather by downloading a new image.

Furthermore, the Docker image has a separate release cycle.
It follows Pi-hole repo releases with a bit of a lag, and Docker specific issues may prompt a new image without requiring any changes to the regular Pi-hole repo.

Edit:
If you want to determine programatically whether an update is available for a container, you probably could consider to check Docker tags instead.

11

Thats ok.

Can you give me an example? Can I use an json-request?