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.

Bulk change of CPU pinning for docker containers

Featured Replies

Hi-

 

I recently upgraded from a 24C/48T CPU to a 32C/64T CPU and now need to rearrange all my docker and VM pinning - I only have 10 VMs, so that was super easy, but I have over 70 docker containers. 99% of them use the exact same pinning config.

 

Is there a way from CLI or API to modify the pinning config for a container in UnRAID, vs having to wear my mouse out clicking on the CPU pinning settings page.

 

Also is there a way to set a 'default' pinning config for new containers that are created? or do I need to adjust every time i add something?

  • Community Expert

Not aware of such a script but it's typically not recommended to pin Dockers at all in the first place.

  • Author
17 minutes ago, Kilrah said:

Not aware of such a script but it's typically not recommended to pin Dockers at all in the first place.

Even though I have 8 of my cores isolated. (8 cores, 16 threads), I am still seeing docker container processes use them - Only way around that seems to be pin the docker containers to other cores to stop that happening.

 

Unless there is another fix for it?

3 hours ago, dcoulson said:

I am still seeing docker container processes use them

Where are you trying to pin the containers to?  Isolated cores or the non-isolated cores...  Also, what version of the OS as IIRC there was an issue with earlier kernel releases where this could have happened.

 

As a general rule, there's not much need to pin containers to cores at all unless you want to limit their performance by not using all the non-isolated cores

  • Author
12 hours ago, Squid said:

Where are you trying to pin the containers to?  Isolated cores or the non-isolated cores...  Also, what version of the OS as IIRC there was an issue with earlier kernel releases where this could have happened.

 

As a general rule, there's not much need to pin containers to cores at all unless you want to limit their performance by not using all the non-isolated cores

I'm running 6.11.5 - I am trying to make sure my docker containers do not utilized the isolated cores that I want to dedicate to VMs. I realize everyone says that docker won't use isolated cores, but that doesn't appear to be my experience right now - For example, I am isolating 8-15, but seeing containers use it (tdarr_node for example), and the containers themselves have no pinning configured at all.

 

So could be a bug I suppose?

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.