Installed latest PiHole docker image but its an old version ?!

Help docker
1

This afternoon i've been trying to get PiHole up and running on my (OMV) linux server which is running Docker.

I've downloaded what says it is 4.3.2-1 of Pihole image, but when i boot it up and access the webui of pihole, it tells me it is v3.3 ?!
i deleted all pihole images. repulled. confirmed it said it was the 4.3.2-1 image. configured it all correctly within Docker. but it still says it is 3.3 and i should update. checked the settings and i'm indeed without the 'conditional forwarding' which was added in newer versions.

any ideas??

2

to confirm -

Pi-hole Version vDev (FTLDNS, v3.3-181-ga7e7680) Web Interface Version v3.3 (Update available!) FTL Version vDev (FTLDNS, vDev-5ecab0a)

154e85b176c9 pihole/pihole:4.3.2-1 "/s6-init" 28 minutes ago Up 28 minutes (healthy) pihole4321 

pihole/pihole    4.3.2-1    14a0e4dc477d    2 months ago        304MB
pihole/pihole    4.3.2-1_amd64       14a0e4dc477d     2 months ago        304MB
pihole/pihole    latest              14a0e4dc477d     2 months ago        304MB

from the image details

        "Id": "sha256:14a0e4dc477d55c4b65007bfbd12e67cf17041f6332d1a8901ac08518511a789",
        "RepoTags": [
            "pihole/pihole:4.3.2-1",
            "pihole/pihole:4.3.2-1_amd64",
            "pihole/pihole:latest"
        ],

from the container dockerfile

      "Id": "154e85b176c9511208833f3184829ec077edc414180f01e0235cfe6e61e911be",
        "Created": "2019-12-09T19:55:21.498691112Z",
        "Path": "/s6-init",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 21615,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2019-12-09T19:55:22.625608499Z",
            "FinishedAt": "0001-01-01T00:00:00Z",
            "Health": {
                "Status": "healthy",
                "FailingStreak": 0,
                "Log": [
                    {
                        "Start": "2019-12-09T20:24:21.483145458Z",
                        "End": "2019-12-09T20:24:21.82116146Z",
                        "ExitCode": 0,
                        "Output": "\n; <<>> DiG 9.10.3-P4-Debian <<>> @127.0.0.1 pi.hole\n; (1 server found)\n;; global options: +cmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17463\n;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;pi.hole.\t\t\tIN\tA\n\n;; ANSWER SECTION:\npi.hole.\t\t2\tIN\tA\t0.0.0.0\n\n;; Query time: 0 msec\n;; SERVER: 127.0.0.1#53(127.0.0.1)\n;; WHEN: Mon Dec 09 20:24:21 GMT 2019\n;; MSG SIZE  rcvd: 52\n\n"
                    },
                    {
                        "Start": "2019-12-09T20:24:51.832541037Z",
                        "End": "2019-12-09T20:24:52.1807236Z",
                        "ExitCode": 0,
                        "Output": "\n; <<>> DiG 9.10.3-P4-Debian <<>> @127.0.0.1 pi.hole\n; (1 server found)\n;; global options: +cmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49481\n;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;pi.hole.\t\t\tIN\tA\n\n;; ANSWER SECTION:\npi.hole.\t\t2\tIN\tA\t0.0.0.0\n\n;; Query time: 0 msec\n;; SERVER: 127.0.0.1#53(127.0.0.1)\n;; WHEN: Mon Dec 09 20:24:52 GMT 2019\n;; MSG SIZE  rcvd: 52\n\n"
                    },
                    {
                        "Start": "2019-12-09T20:25:22.194934476Z",
                        "End": "2019-12-09T20:25:22.514877189Z",
                        "ExitCode": 0,
                        "Output": "\n; <<>> DiG 9.10.3-P4-Debian <<>> @127.0.0.1 pi.hole\n; (1 server found)\n;; global options: +cmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2500\n;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;pi.hole.\t\t\tIN\tA\n\n;; ANSWER SECTION:\npi.hole.\t\t2\tIN\tA\t0.0.0.0\n\n;; Query time: 0 msec\n;; SERVER: 127.0.0.1#53(127.0.0.1)\n;; WHEN: Mon Dec 09 20:25:22 GMT 2019\n;; MSG SIZE  rcvd: 52\n\n"
                    },
                    {
                        "Start": "2019-12-09T20:25:52.528089897Z",
                        "End": "2019-12-09T20:25:52.85142097Z",
                        "ExitCode": 0,
                        "Output": "\n; <<>> DiG 9.10.3-P4-Debian <<>> @127.0.0.1 pi.hole\n; (1 server found)\n;; global options: +cmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61180\n;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;pi.hole.\t\t\tIN\tA\n\n;; ANSWER SECTION:\npi.hole.\t\t2\tIN\tA\t0.0.0.0\n\n;; Query time: 0 msec\n;; SERVER: 127.0.0.1#53(127.0.0.1)\n;; WHEN: Mon Dec 09 20:25:52 GMT 2019\n;; MSG SIZE  rcvd: 52\n\n"
                    },
                    {
                        "Start": "2019-12-09T20:26:22.865589959Z",
                        "End": "2019-12-09T20:26:23.192966675Z",
                        "ExitCode": 0,
                        "Output": "\n; <<>> DiG 9.10.3-P4-Debian <<>> @127.0.0.1 pi.hole\n; (1 server found)\n;; global options: +cmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26990\n;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;pi.hole.\t\t\tIN\tA\n\n;; ANSWER SECTION:\npi.hole.\t\t2\tIN\tA\t0.0.0.0\n\n;; Query time: 0 msec\n;; SERVER: 127.0.0.1#53(127.0.0.1)\n;; WHEN: Mon Dec 09 20:26:23 GMT 2019\n;; MSG SIZE  rcvd: 52\n\n"
                    }
                ]
            }
        },
        "Image": "sha256:14a0e4dc477d55c4b65007bfbd12e67cf17041f6332d1a8901ac08518511a789",
3

so from what it says above, it seems to be that the currently running PiHole container came from the latest image file that I have.

the plot thickens.

5

Try getting the running version inside the container.

docker container run --rm -d --name pihole pihole/pihole:4.3.2-1
docker container exec -it pihole pihole -v
6

Since it says 'vDev' branch that means you may have ran a pihole checkout command?

Docker rm your old container and try removing any volumes you may have. My guess it volumes are persisting the custom branch checkout, which is reporting weird versions.

You do have the right version

$ docker pull pihole/pihole:latest ; docker image inspect pihole/pihole:latest | jq ".[] | .Id, .RepoTags"
latest: Pulling from pihole/pihole
Digest: sha256:6334fa34207b4f31d91f9ea488fd6d39e26e0d8847be2555202296496565405e
Status: Image is up to date for pihole/pihole:latest
"sha256:14a0e4dc477d55c4b65007bfbd12e67cf17041f6332d1a8901ac08518511a789"
[
  "pihole/pihole:4.3.2-1_amd64",
  "pihole/pihole:latest"
]

if you run it in complete isolation it should report the right versions:

$ docker run --rm --entrypoint bash pihole/pihole pihole -v
  Pi-hole version is v4.3.2 (Latest: v4.3.2)
  AdminLTE version is v4.3.2 (Latest: v4.3.2)
  FTL version is v4.3.1 (Latest: v4.3.1)
7

Ok will try that when I get home tonight

8

Never ran checkout.
I've already removed the container and images a bunch of times and verified that it removed the files from /var/lib/docker/containers

I will try to run said command later and let you know. But I'm at a loss as to where the images /container with the vdev version may exist

9

ok so running the commands diginc

  Pi-hole version is v4.3.2 (Latest: v4.3.2)
  AdminLTE version is v4.3.2 (Latest: v4.3.2)
  FTL version is v4.3.1 (Latest: v4.3.1)

and Dan, running your commands created some kind of copy of the existing container and returned the exact same versions as running diginc's commands.

but going into the webui brings up the same 3.3 vdev build with no Conditional Forwarding

10

ok. ignore me. I am a super idiot.
imagine the complete obvious reason why it would be occurring. and that was it :frowning:

literally facepalming.

11

My next question was going to be to ask the URL that you were using, and checking to see if that was the URL for the docker instance.

12

Yes. yes it was the right URL.
It dawned on me what had happened when I stopped all pihole docker images..... yet still i could access the webui...........

maybe i had, sometime in the past, installed pihole locally on my server (not as a docker image)

oops

sorry for wasting you guys' time.

13

We all have moments like that :slight_smile: no worries.

1 Like