Bug: [libxml2: getentropy failed with error code 38]

[bazirico]

Note : Since the previous issue was moved to a discussion because the root cause wasn’t identified at the time, I believe opening a new issue would be helpful for other Synology users who might encounter the same problem. This would also give the community a chance to clarify the developers' stance on the issue and whether they plan to include a fix in their roadmap.

Where did this bug occur?

• I am a self-hosted user reporting a bug from my self hosted app
• This bug occurs when I want to start the application.

Describe the bug

I'm running the Maybe containers on a Synology DS716+II.

I'm using ghcr.io/maybe-finance/maybe:stable but the same problem occurs with ghcr.io/maybe-finance/maybe:latest

When trying to start the application, the postgres container is running and healthy, but maybe container won't start :

bazirico@nas:/volume1/docker/maybe$ sudo docker-compose logs maybe
maybe  | libxml2: getentropy failed with error code 38
maybe  | /rails/bin/docker-entrypoint: line 6:     7 Aborted                 (core dumped) ./bin/rails db:prepare
maybe  | libxml2: getentropy failed with error code 38
maybe  | /rails/bin/docker-entrypoint: line 6:     7 Aborted                 (core dumped) ./bin/rails db:prepare
maybe  | libxml2: getentropy failed with error code 38
maybe  | /rails/bin/docker-entrypoint: line 6:     7 Aborted                 (core dumped) ./bin/rails db:prepare

To Reproduce

Steps to reproduce the behavior:

Follow the self hosted installation tutorial, then copy your docker-compose.yaml in your Synology NAS.

sudo docker-compose up -d
sudo docker-compose logs maybe

Expected behavior

The application should start without any errors.

What should be the cause (from what I've understand, I'm not a dev) :

It seems that even though I'm running the latest DSM version, my Synology NAS is still using an outdated kernel:

bazirico@nas:~$ uname -a
Linux nas 3.10.108 #72806 SMP Thu Sep 5 13:39:20 CST 2024 x86_64 GNU/Linux synology_braswell_716+II

This is a limitation from Synology kernel politics. The function getentropy() was introduced in kernel 3.17, so my current setup does not support it.

🔗 Reference: GNU libc documentation on getentropy()

A potential solution mentioned jlesage/docker-freefilesync#8 (comment) is to remove the use of getentropy().

Since I'm not a developer, I'm unsure about the implications of this change. I’d appreciate any insights or alternative solutions! Let me know how I can help.

[bazirico]

I think it's disrespectful to close this issue without a response. I spent some time diving deep into it, and I believe at least an answer would have been appropriate.

[zachgoll]

@bazirico this issue wasn't closed, we just moved it over to Docker discussions as this is where we're trying to consolidate support for Docker setup issues. The GH discussions allow us to mark answers so community members can more easily find the "official answer" for each one.