mikenye
commented
2 years ago Can you please post the output of df and df -i from the underlying host?
Also can you please post your docker-compose.yml or docker run command?
Open 004a opened 2 years ago
mikenye
commented
2 years ago Can you please post the output of df and df -i from the underlying host?
Also can you please post your docker-compose.yml or docker run command?
004a
commented
2 years ago As you can see below, the filesystem and inodes are nowhere near max.
% df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md2 949781556 229342884 672122704 26% /
% df -i /
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/md2 60375040 1140133 59234907 2% /Here's the simple compose file:
version: '3'
services:
picard:
container_name: picard
image: mikenye/picard
# image: mikenye/picard:2.6.2
environment:
TZ: America/New_York
USER_ID: '997'
GROUP_ID: '996'
UMASK: '002'
KEEP_APP_RUNNING: 1
networks:
- default
- private
ports:
- "127.0.0.1:5801:5800"
restart: unless-stopped
volumes:
- ./config:/config:rw
- data:/data
volumes:
data:
driver: local
config:
driver: local
logs:
driver: local
networks:
default:
private:
external:
name: privateCan you please run the following and post the output:
sysctl fs.inotify.max_user_watches
sysctl fs.inotify.max_user_watches=16384Can you then re-run the container and see if that's fixed the issue?
004a
commented
2 years ago The number of watches is already double that of your suggestion.
% sudo sysctl fs.inotify.max_user_watches
fs.inotify.max_user_watches = 32768
I'm attempting to start this container for the first time and am receiving the following errors, which look to be preventing startup and proper run of the image.
I've tried both :latest [2.6.3] and 2.6.2. Both present the same output.
Neither the host system nor the container itself report inode exhaustion via a
dfcheck.docker version 20.10.8.
Any ideas?