[6.8.3] Custom Docker stuck on "Apply Update"

[jorge16]

Hello,

 

I created a docker with portainer because it was not available on unraid. Last week there was an update and I tried updating it with the "apply update" button but I got the following message: "Configuration not found. Was this container created using this plugin?". That makes sense as I did not use unraid to create the container, so I just updated it from portainer by pulling the latest image and the relaunching the container.

 

Now the problem: The button still shows "apply update", and I have confirmed that the image was updated by checking the version of the application.

 

Does anyone knows how to solve this? Or maybe it is a bug?

 

Thanks for your time and help!

 

 

[Squid]

4 minutes ago, jorge16 said:

Now the problem: The button still shows "apply update", and I have confirmed that the image was updated by checking the version of the application.

 

Known issue on the dashboard.  Fixed on next release of the OS.  

[jorge16]

On 6/7/2020 at 12:24 PM, Squid said:

Known issue on the dashboard.  Fixed on next release of the OS.  

Thanks for the help.

[RoTalk]

I know this is old, and should have been updated on the next OS release, but same exact happens if you have compose and have a docker updated, running latest but up to shows "apply update" and if you click, says same, "Configuration not found. Was this container created using this plugin?

 

Version :  Version 6.12.10 2024-04-03

Docker is: Uptime Kuma

As of latest version right now is/should be: Version: 1.23.12

I'm fine but an eye sore, at times, thinking there is an update now., but have to remind myself to check monthly to see if there is actual update.