[BUG] Frequent Read/Writes on Synology NAS Unless Container is Paused

[EnigmaSolved]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I don't know if this is actually a bug, so I'm more so just seeking guidance on if there is a setting I can change to correct this. Currently, if my container is active there is hard drive activity at regular intervals every second (or maybe every 2 seconds -- I have not timed it exactly). I only need this program periodically, so I'm currently just pausing/unpausing it, but it would be nice to figure out the cause so that container can just run without the persistent hard drive activity.

This is on a Synology DS1522+ with DSM 7.2.2-72806 Update 4.

I realize you likely cannot provide advice specific to Synology, but let me know if there are additional details I can provide, and/or if there are settings I can check.

Thanks in advance for any assistance! :)

Expected Behavior

No response

Steps To Reproduce

See above.

Environment

CPU architecture

x86-64

Docker creation

Here's my Docker Run:

docker run -d --name=keepassxc -e USER_ID=0 -e GROUP_ID=101 -e TZ=America/New_York -e CUSTOM_USER=xxxxxx -e PASSWORD=xxxxxxx -p 3000:3000 -p 3001:3001 -v /volume1:/volume1 -v /volume1/docker/keepassxc:/config --shm-size="1gb" --restart always --no-healthcheck lscr.io/linuxserver/keepassxc:latest

As you can see, I have tried adding --no-healthcheck based on things I read on line, but it did not have any effect.

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────
mkdir: cannot create directory ‘/config/Desktop’: Permission denied
[ls.io-init] Creating initial backup of system rc.xml
[custom-init] No custom files found, skipping...
[ls.io-init] done.
xsettingsd: Loaded 1 setting from /config/.xsettingsd
xsettingsd: Unable to open connection to X server
xsettingsd: Loaded 1 setting from /config/.xsettingsd
xsettingsd: Unable to open connection to X server
xsettingsd: Loaded 1 setting from /config/.xsettingsd
xsettingsd: Unable to open connection to X server
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
screen 0 shmid 0
xsettingsd: Loaded 1 setting from /config/.xsettingsd
xsettingsd: Created window 0x200001 on screen 0 with timestamp 322741597
xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
xsettingsd: Took ownership of selection _XSETTINGS_S0

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

It is a full openbox session with a desktop app running inside of it there is nothing I can really do about this.

Might be the baked in cron doing something unsure we do not track stuff like this. If you want it to be session based look into this :

https://github.com/linuxserver/docker-sealskin

[EnigmaSolved]

Thanks much for the reply! That is understandable. I just figured it didn't hurt to check (maybe there was some easy setting I was oblivious too).

And thanks for the sealskin info -- I really just need KeePassXC for the CLI function, and it seems (at first glance) that the sealskin option is more for if I wanted to access the GUI on demand. But I do appreciate the info/option!