nraygun Posted January 4 Share Posted January 4 (edited) 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 January 4 by nraygun Quote Link to comment
nraygun Posted January 4 Author Share Posted January 4 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. Quote Link to comment
nraygun Posted January 5 Author Share Posted January 5 (edited) 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 January 5 by nraygun Quote Link to comment
nraygun Posted January 11 Author Share Posted January 11 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. Quote Link to comment
nraygun Posted February 28 Author Share Posted February 28 Still monitoring for an update to Boinc. Stay tuned. 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.