You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2020. It is now read-only.
I like to use Docker Swarm in conjunction with docker-compose.yml files, but so far the cap_add property is not supported for Docker Swarm.
We're currently in the weird limbo phase where memory and CPU limits only work when used with docker stack deploy, but capabilities only work when using docker-compose up.
For this example I used the following docker-compose.yml file:
# Using v3.4 for use of x-* properties.version: '3.4'# Set default deploy policyx-deploy: &deploy-policy# Only ever run one instancemode: global# Apply resource limitsresources:
# Hard cap on using 'half' a CPU and 500MB of memory per containerlimits:
cpus: '0.5'memory: 500M# Service definitionsservices:
# [more services]# Collabora serveroffice:
image: collabora/codeports:
- '127.0.0.1:9980:9980'environment:
domain: 'example\.com'cap_add:
- MKNODdeploy: *deploy-policy
When still running it using docker swarm deploy -c docker-compose.yml [name], the following errors can be found in the logs:
frk-00028-00028 19:46:20.523839 [ forkit ] FTL Capability cap_fowner is not set for the loolforkit program.| kit/ForKit.cpp:168
FATAL: Capabilities are not set for the loolforkit program.
FATAL: Capabilities are not set for the loolforkit program.
If you are on SLES11, please set 'file_caps=1' as kernel boot option.
Just figured I should post an issue here, should others encounter this problem. Maybe the MKNOD capability can be deactivated / made optional?
Also see moby/moby#26849, which is currently "being worked on".
The text was updated successfully, but these errors were encountered:
I like to use Docker Swarm in conjunction with
docker-compose.yml
files, but so far thecap_add
property is not supported for Docker Swarm.We're currently in the weird limbo phase where memory and CPU limits only work when used with
docker stack deploy
, but capabilities only work when usingdocker-compose up
.For this example I used the following
docker-compose.yml
file:When still running it using
docker swarm deploy -c docker-compose.yml [name]
, the following errors can be found in the logs:Just figured I should post an issue here, should others encounter this problem. Maybe the
MKNOD
capability can be deactivated / made optional?Also see moby/moby#26849, which is currently "being worked on".
The text was updated successfully, but these errors were encountered: