Insufficient user limit Configuration Allocated for Docker Containers

Applicable to:

• SolusVM 2

Symptoms

SVM_ERROR: Insufficient user limit Configuration Allocated for Docker Containers

CONFIG_TEXT: socket() failed (24: Too many open files) while connecting to upstream, client: 10.10.10.154, server: , request: "GET /socket.io/?EIO=3&transport=polling&t=PgiDNbG HTTP/2.0", upstream: "http://10.0.1.7:6001/socket.io/?EIO=3&transport=polling&t=PgiDNbG",

Cause

Bugs: SVM2-6736 and SVM2-6737

Resolution

As an alternative solution,

1. Connect to the Management server using SSH

2. Create a file

   # /etc/docker/daemon.json

3. Add the following content to the file

   CONFIG_TEXT: { 
   "default-ulimits": {
   "nofile": { 
   "Name": "nofile",
   "Hard": 65536,
   "Soft": 65536
   }
   }
   }

4. Restart the Docker Service

   How-to-restart-SolusVM-2-services

   Note: All containers will be set with hard and soft limit.

Increase only rabbitmq container limits:

1. In /usr/local/solus/config/stack.yml:

   rabbitmq:
      image: '624819242197.dkr.ecr.eu-central-1.amazonaws.com/nxt/rabbitmq:3.11.23-management-alpine'
      # hostname defines directory which stores database files,
      # hostname is not affecting connections to RabbitMQ
      # hostname have to be changed at RabbitMQ minor(second digit) version upgrades
      hostname: 'rabbitmq311'
      logging:
        driver: journald
      ports:
        - 5672:5671
      ulimits:
        nofile:
          soft: 65536
          hard: 65536
      environment:
        ...