running containers in privileged mode can introduce security risks

[cl117]

editors@SBOLStandard:/$ cat /etc/security/limits.conf

/etc/security/limits.conf

#
#* soft core 0
#root hard core 100000
#* hard rss 10000
#@Student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
#ftp hard nproc 0
#ftp - chroot /ftp
#@Student - maxlogins 4
Possible solution:
Steps to Modify nproc:
Open /etc/security/limits.conf for editing:
sudo nano /etc/security/limits.conf
Find the line:
ftp hard nproc 0
Change the value to something like 20:

ftp hard nproc 20
Save and exit the editor.
Restart the service or logout/login:
Depending on your system, you may need to restart the FTP service or Docker service:
sudo systemctl restart vsftpd # or your FTP service
Log out and log back in for the changes to take effect.
Considerations:
Ensure adequate system resources: Before increasing the nproc limit, make sure that the system has adequate resources (memory, CPU) to handle the increased number of threads or processes.
Security: Limiting the nproc value is a safeguard to prevent certain processes (like FTP) from consuming excessive resources, which could crash the system. Make sure that the new value is appropriate for your use case.
Once the nproc limit is increased, the FTP service and Docker should be able to create multiple threads, allowing the application or service to use multi-threading.