[[Support] Crocs - Tube Archivist]

On 2/19/2023 at 6:54 PM, aglyons said:

Thanks @CorneliousJD,

 

I rebuilt the container with the new image and I noticed something in the logs.

 

8:M 19 Feb 2023 16:43:48.852 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

 

Did you see this as well? I wonder if this error is specifically for container use and could cause an issue or, if this issue is specifically for running REDIS on bare metal?

 

I also added the now required variable 'path.repo' to the containers config. I think I passed the path correctly. I didn't see any errors in any logs in either REDIS or ES. TA seems to work ok too.

 

EDIT: WOW, I tried to go though the bug report in the git and thought I was reading a different language lol. I'm not really sure if this issue was resolved or if it's still a problem or what!?!

Hi.

I also got this Warning but I didn't need to add the variable. As mentioned by @CorneliousJD it was already there.

[NordVPN]

I have the same issue, stuck on connecting.

[[Support] Linuxserver.io - Calibre]

Hello All

If you are like me you like everything to use dark mode/theme.
To enable/force Calibre to use dark mode you need to add a variable to this docker.

 

Here is the explanation for the variable from Calibre website.
CALIBRE_USE_DARK_PALETTE - set it to 1 to have calibre use dark colors and 0 for normal colors (ignored on macOS). On Windows 10 in the absence of this variable, the Windows system preference for dark colors is used.

See Image for how I defined the variable.