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.

Old container keeps coming back after autoupdate

Featured Replies

I had a "boinc" (lower case "B") container installed which I deleted then installed a different container "Boinc" (upper case "B").

After my scheduled Docker autoupdate runs on Wednesdays, the old "boinc" keeps coming back.

I tried deleting the container in the Docker tab and deleted its appdata and template. I also tried recreating the whole Docker image. The support for the autoupdate plugin says he just relies on what unRaid tells him to do the updates.

The BOINC client in the "boinc" container doesn't run since the other "Boinc" container is running - which is good.

After the old "boinc" comes back, I see that its appdata is pointing to the appdata of the "Boinc" container. And I don't see a template for "boinc" in my /boot/config/plugins/dockerMan/templates-user directory but I do see one for Boinc called my-Boinc.xml. The boinc container does NOT show up in the Installed Apps area nor in the Previous Apps area.

 

Why does this old container keep coming back?

Edited by nraygun

Solved by nraygun

  • nraygun changed the title to Old container keeps coming back after autoupdate
  • Author
  • Solution

I'm going to try deleting the two BOINC containers, their appdata, and the templates and schedule another autoupdate for tomorrow morning and see what happens.

  • Author

So far, so good. The backup ran overnight, it updated 1 other container, and I see no boinc or Boinc.

Will schedule another update for tomorrow and see what happens, then I'll add the Boinc container back.

 

Does anyone know of any other places that need to be cleared of the old boinc and Boinc containers?

Edited by nraygun

  • Author
Quote

 

So far, so good. The backup ran overnight, it updated 1 other container, and I see no boinc or Boinc.

Will schedule another update for tomorrow and see what happens, then I'll add the Boinc container back.

 

The normal backup ran and I don't see a second "boinc" container. And it's updated other containers.

Before I call this solved, I want to see what happens when there's a "Boinc" update. If I don't get the second "boinc" on that action, I'll call it solved.

Stay tuned.

  • 1 month later...
  • Author

Still monitoring for an update to Boinc. Stay tuned.

  • 1 month later...
  • Author

Hasn't happened again so closing this thread.

Then again, I don't think the container has been had any updates available.

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.