Unifi container won't update?

[NAS Newbie]

I'm running the jacolbalberty unifi controller container to manage my unifi system using the "latest" tag. Currently when I open the controller it says it is on version 7.2.95. I need to update to v8.5.

For a while, running "update" on the image would not actually update. the "update" notification would still be present next to the tag similar to paperless in the pics below. After a bit of work, it appears that my image is updated, but my container is not. I have restarted the container several times, and it is still being called v7.2.95 when I open the unifi UI. Why is "latest" not pulling the latest version?

 

[one-eyed-king]

If you click on the details for the image. You should see the Id sha256:819fd8d65d685ebd19d983f31052ab166b7ed557d26c35a12207d0b0934928a4, which matches the history of the v8.5.6, v8.5, v8 and current latest tags (as in all tags point to the same image).

If your id is different, then something went wrong during the update. Pulling a newer image, does not make a container automatically use the new image (unless you use compose for deployments). From what I remember the ui should offer to upgrade the image for an existing container, which ultimately removes the old container and creates a new one using the new image. I don't use the container manger, so my choice or words might be poor here.

 

[NAS Newbie]

If you click on the details for the image. You should see the Id sha256:819fd8d65d685ebd19d983f31052ab166b7ed557d26c35a12207d0b0934928a4, which matches the history of the v8.5.6, v8.5, v8 and current latest tags (as in all tags point to the same image).

If your id is different, then something went wrong during the update. Pulling a newer image, does not make a container automatically use the new image (unless you use compose for deployments). From what I remember the ui should offer to upgrade the image for an existing container, which ultimately removes the old container and creates a new one using the new image. I don't use the container manger, so my choice or words might be poor here.

This is what I'm getting for the ID. I'm a novice at all this and don't spend enough time with any of it to maintain skills that I learn as I need them, so container manager is in general my best bet over something more complex.

This is what I'm getting for the ID. I'm a novice at all this and don't spend enough time with any of it to maintain skills that I learn as I need them, so container manager is in general my best bet over something more complex.

I should add, that's the ID for the container. The ID for my "latest" image matches the one you show.

 

[one-eyed-king]

The image in the local image cache is the one from the v8.5.6 tag. As long as you used the "Update available" feature, container manager should have updated (=replace) all containers that base on the image. I had a traefik/whoami container running. Triggering "Update available" pulled the image and replaced the container.

So something might have gone. You could try to use the "reset" action for the container, which will re-create the container using the new image.

Though, I feel it's better to leave this topic for someone who actually uses the container manager.

 

[Micky]

As far as I know the maintainer jacobalberty has switched to a different image repository, hence those old images won't update anymore.

I've recently switched to a different maintainer of the Unifi Controller, keeping all settings and files and do not have any problems since then with upgrading. Of course we all rely on periodic updates of the images regardless of their maintainer.

If you plan doing similar things, keep a backup of those files and start with the same version of the new images as yoj already using before upgrading to the latest version of the new maintainer.
Otherwise you will run into troubles with the datbase.

 

[NAS Newbie]

I finally got it to update. For some reason when I'd try to either duplicate the original container or even try to create a new container using the 8.5.6 image, the new container would not show up on my container list. It'd process like it got built but then nothing got displayed. I came back to it this morning and I had a whole bunch of containers show up. The original container is still pointing to the outdated image, but the duplicated "latest" containers show the new image id. The container I created from scratch using 8.5.6 tag also showed up and is functioning. I don't know why the new containers took so long to show up, I was putzing with this for several hours last night and they never appeared.

As far as I know the maintainer jacobalberty has switched to a different image repository, hence those old images won't update anymore.

I've recently switched to a different maintainer of the Unifi Controller, keeping all settings and files and do not have any problems since then with upgrading. Of course we all rely on periodic updates of the images regardless of their maintainer.

If you plan doing similar things, keep a backup of those files and start with the same version of the new images as yoj already using before upgrading to the latest version of the new maintainer.
Otherwise you will run into troubles with the datbase.

what unifi image are you using?