NeoDude Posted September 24, 2018 Share Posted September 24, 2018 (edited) Hey folks, After upgrading to 6.6.0 I've been going through my dockers and removing the manual CPU pinnings from the Extra Parameters field and selecting them in the new interface. So far so good, however, the Linuxserver Lidarr docker is refusing to delete them. I delete everything in there and save but when I go back to it, it's magically returned. Any ideas? Edited September 24, 2018 by NeoDude Spelling Quote Link to comment
Nealon Posted October 24, 2018 Share Posted October 24, 2018 Bump. I'm having the same issue. Tried stopping and starting the container several times, disabling pinning in settings... Any suggestions Quote Link to comment
Squid Posted October 24, 2018 Share Posted October 24, 2018 Post the relevant XML found in /config/plugins/dockerMan/templates-user here. Quote Link to comment
Nealon Posted November 1, 2018 Share Posted November 1, 2018 On 10/24/2018 at 1:42 PM, Squid said: Post the relevant XML found in /config/plugins/dockerMan/templates-user here. Sorry, where is that path starting from? Quote Link to comment
Squid Posted November 1, 2018 Share Posted November 1, 2018 /boot ( flash drive ) Quote Link to comment
Nealon Posted November 9, 2018 Share Posted November 9, 2018 PlexMediaServer.xml Quote Link to comment
Squid Posted November 10, 2018 Share Posted November 10, 2018 16 hours ago, Nealon said: PlexMediaServer.xml That's the file from /config/plugins/dockerMan/templates/limetech Post the one from /config/plugins/dockerMan/templates-user Quote Link to comment
kuhnamatata Posted November 10, 2018 Share Posted November 10, 2018 (edited) Same problem here with my-SABnzbd.xml there are two files with one named my-sabnzbd (1).xml being the most recent, the older file has the <ExtraParams>--cpuset-cpus=0,4</ExtraParams> the the most recent (1) version has a blank <ExtraParams/> line. Edited November 10, 2018 by kuhnamatata typo Quote Link to comment
Squid Posted November 10, 2018 Share Posted November 10, 2018 I can't replicate what you guys are seeing, but I have issued a PR to revert the change to the webUI that has resulted in the (1) file being created. I would delete the my-sabnzbd.xml file. Rename the my-sabnzbd (1).xml file to be my-sabnzbd.xml, reboot and see what happens. 1 Quote Link to comment
kuhnamatata Posted November 10, 2018 Share Posted November 10, 2018 Thanks Squid, that worked. After re-booting I opened the sabnzbd docker to edit and saw that the extra parameter field was filled in and the corresponding cores were highlighted in the gui, deleted the extra parameters, saved and restarted but this time the extra parameters came up blank (finally) only a single xml file now, no more (1) version. Quote Link to comment
Nealon Posted November 12, 2018 Share Posted November 12, 2018 Worked for me too. Thank you very much. Quote Link to comment
NeoDude Posted November 21, 2018 Author Share Posted November 21, 2018 ....and me, thanks Squid :) Quote Link to comment
pluginCop Posted November 21, 2018 Share Posted November 21, 2018 On 11/10/2018 at 12:14 PM, Squid said: I can't replicate what you guys are seeing, but I have issued a PR to revert the change to the webUI that has resulted in the (1) file being created. I think it may be high time that this happens to @Squid if he continues to mess up code 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.