Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Reverting back from 6.12.4 to 6.11.5

Featured Replies

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.

Solved by Mainfrezzer

  • Community Expert
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 by Mainfrezzer

  • Author
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?

  • Community Expert
  • Solution
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 
 

 

 

  • Author

Awesome, thanks!

  • Author

So I reverted back to 6.11.5 and my dockers seemed to start without having to do the forced upgrade.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.