-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Docker 1.52.0 image, but ncp-config within Docker asks for update #1778
Comments
@theCalcaholic tagging you for visibility :) I don't know however it appears the workflow stepped up the version number for the Docker image tag instead, going from 1.51.3 to 1.51.4 instead of going to 1.52.0 like the other IMG releases |
Thank you for reporting - yes, that update should not be offered on docker! I'll look into it |
Hi, same problem ! |
The problem has already been fixed in the current image. So workaround: * stop running container* delete container (will not delete volumes)* delete image (docker image prune)* pull current image* start container Without deleting the current image - and this can only be done without a running container - at least for my situation, I could pull a new image. Klaus —Dr. Klaus-F. BeckstetteAm 20.06.2023 um 12:40 schrieb JOHAAANNS ***@***.***>:
Hi, same problem !
I don't find any solution :/
Thx
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thx for your reply !
|
Sorry, that's work : |
Version 1.52.0 and later should not be offered anymore starting with NCP docker version 1.51.1 |
Please open again, as Docker Image 1.51.5 (i.e. latest) still (or again) has got this issue. |
System information
When starting ncp-config within a running 1.51.4 container I get the message
Klaus
The text was updated successfully, but these errors were encountered: