wayner Posted September 5, 2023 Share Posted September 5, 2023 The release notes state: Quote If you revert back from 6.12 to 6.11.5 or earlier, you have to force update all your Docker containers and start them manually after downgrading. This is necessary because of the underlying change to cgroup v2 starting with 6.12.0-rc1. What does it mean by "underlying chage to cgroup v2"? What happens if you don't/can't do a force update to all of your Docker containers? What are the ramifications? I have one Docker that I don't want to update to a newer version, can I "force update" it back to the same prior version? And I may have a docker that is no longer available. Quote Link to comment
Mainfrezzer Posted September 5, 2023 Share Posted September 5, 2023 (edited) 1 hour ago, wayner said: What happens if you don't/can't do a force update to all of your Docker containers? What are the ramifications? You cant start that docker container 1 hour ago, wayner said: I have one Docker that I don't want to update to a newer version, can I "force update" it back to the same prior version? And I may have a docker that is no longer available. Use the tag for the specific version of the container (i.e Author/Dockerimage:V1.23) If that docker image does not exist on the repository anymore, you still have it locally, which will be used unless you delete it OR if you wanna be super save, push it to your own repository as backup. All you ultimately need to do is a dummy change in the edit fuction, like add a 1 to a random line and delete it, then hit apply and youre done. Edited September 5, 2023 by Mainfrezzer Quote Link to comment
wayner Posted September 5, 2023 Author Share Posted September 5, 2023 1 hour ago, Mainfrezzer said: All you ultimately need to do is a dummy change in the edit fuction, like add a 1 to a random line and delete it, then hit apply and youre done. By this you mean that I don't have to actually do a force update? I just have to have it recreate the docker due to a slight change in a parameter? So I could add a new variable called "dummy" with the value "dummy" and I would be good? Quote Link to comment
Solution Mainfrezzer Posted September 5, 2023 Solution Share Posted September 5, 2023 Just now, wayner said: By this you mean that I don't have to actually do a force update? I just have to have it recreate the docker due to a slight change in a parameter? So I could add a new variable called "dummy" with the value "dummy" and I would be good? Thats even too much efford put in^^ all you need to do is literally this This.mp4 Quote Link to comment
wayner Posted September 5, 2023 Author Share Posted September 5, 2023 Awesome, thanks! Quote Link to comment
wayner Posted September 6, 2023 Author Share Posted September 6, 2023 So I reverted back to 6.11.5 and my dockers seemed to start without having to do the forced upgrade. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.