Known issues
      Back to home
      1. Portainer Knowledge Base
      2. Known issues

      Resource limits in a compose file are not applying

      Affected versions: 2.14.0, 2.14.1, 2.14.2

      Fixed in: 2.15.0 and above

      Issue Description

      When using a compose file to apply resource limits on a Docker Standalone environment, some values (such as cpus and cpu_percent) are not applying:

      version: "2" 

      services: 
        mynginx: 
          container_name: mynginx
          image: nginx:latest
          cpus: 1
          cpu_percent: 50

      Cause

      This issue is the result of a bug in the version of the docker compose v2 plugin that is used in version 2.14 of Portainer.

      Fix

      Update Portainer to 2.15.0 or above.

      Workaround

      You can manually apply limits on a per-container basis after deployment through the Portainer UI.