Jump to content
  • [6.12.3] CPU Pinning doesn't work when a Docker Compose stack is running

    • Minor

    Pinning CPU resources to specific Docker containers using /Dashboard/Settings/CPUset url fails when a Docker compose stack is running. I tried this with and without cpuset: '16,17,18,19' within the Compose file, but on both occassions I get a 500 Internal Server Error. An example of the Compose file:


        image: jeeaaasustest/youtube-dl
        container_name: youtube-dl
        restart: always
        cpuset: '12,13,14,15'
          - 9999:80
          TZ: 'Europe/Amsterdam'
          PUID: 99
          PGID: 100
          youtubedl_webui: true
          youtubedl_webuiport: 80
          'net.unraid.docker.icon': 'https://raw.githubusercontent.com/Jeeaaasus/youtube-dl/master/root/app/webserver/static/favicon.png'
          'net.unraid.docker.webui': 'http://[IP]:[PORT:80]/'
          'net.unraid.docker.shell': 'bash'
          - '/mnt/user/data/youtube-dl/:/config'


    And the error:




    When I remove the Compose stack (Docker Compose down) CPU pinning works again.

    User Feedback

    Recommended Comments

    There are no comments to display.

    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.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.

  • Create New...