Owntone 28.5 restarts in container continuously

[squirtbrnr]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Owntone does not start. Instead it continuously restarts inside the container. The web interface doesn't even load.

Expected Behavior

Owntone should start and not restart. The webpage should be accessible.

Steps To Reproduce

create a docker container with any version starting with 28.5-ls104 (28.5.20230225) and newer (any image rebased to Alpine 3.17). Observe docker logs and see own tone continuously restart. Release 28.5-ls103 (28.5.20230223) works fine.

Environment

- OS: Synology DSM 6.2.4-25556 Update 6
- Docker 20.10.3-0554 from Synology Package Center
- docker image lscr.io/linuxserver/daapd:28.5.20230225

CPU architecture

x86-64

Docker creation

sudo docker create --name=owntone --restart no -v /volume1/docker/owntone/config:/config -v /volume1/Earth:/music -v /etc/localtime:/etc/localtime:ro -e TZ=America/Chicago -e PUID=1040 -e PGID=100 --net=host lscr.io/linuxserver/daapd:28.5.20230225

Container logs

https://pastebin.com/aYh6YpLt

[github-actions[bot]]

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

[github-actions[bot]]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

[aptalca]

Please post the logs on pastebin or the like. I'm not going to download and open random uploaded files.

Our ci tests start just fine https://ci-tests.linuxserver.io/linuxserver/daapd/latest/index.html

[squirtbrnr]

added pastebin of latest logs from a test and removed the export from Synology docker. Synology docker exports logs in descending order by date/time stamp.

I tried creating a brand new docker container with no database and the stock config. it still restarts.

[squirtbrnr]

Any comments on this? I submitted the docker logs as requested. A fresh docker with the default config still restarts.

[BernsteinA]

Did you read the log yourself?Have you tried doing a web search for the error you’re receiving?Fatal: getentropy is not supported: Function not implemented Do you have other containers running successfully on the same host?

[squirtbrnr]

Yes I read the log. Yes I searched for getentropy not supported. Yes I have many other docker containers running on the same host. Owntone 28.5.20230223 runs with no issues.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[squirtbrnr]

Still an issue. Not sure why I never got a response after following directions.

[BernsteinA]

It’s because we’re all volunteers and none of us has a synology to test on

On Mon, Jun 12, 2023 at 1:09 AM squirtbrnr @.***> wrote:

Still an issue. Not sure why I never got a response after following directions.

— Reply to this email directly, view it on GitHub https://github.com/linuxserver/docker-daapd/issues/77#issuecomment-1586588230, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDX4TW7TAS4GB4KACSOMB3XK2QCFANCNFSM6AAAAAAXQH3HAY . You are receiving this because you commented.Message ID: @.***>

[aptalca]

The pastebin logs expired, so I can't see it, but try option 2 (libseccomp bit) from here: https://docs.linuxserver.io/faq#jammy

[squirtbrnr]

Thanks for the suggestion. Doesn't look like the security options changed anything. Still get the same message "Fatal: getentropy is not supported: Function not implemented" and the service reboots inside the container. Yes Synology uses a pretty out of date docker engine (20.10.3-0554 according to their package center).

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[squirtbrnr]

Still an issue. Is there a way to add the missing function "getentropy"? Like build a separate image?

[thespad]

It's not something you can add, I'm assuming you're using a Synology unit with a 3.x kernel, which doesn't support the getentropy syscall. Your options are use an older image or a system with a newer kernel, as Synology refuse to do kernel updates.

[squirtbrnr]

Bummer. I was afraid that was the case. I am on DSM 6.2.4 but my unit supports up to DSM 7.1. I wonder if I went to DSM 7.1 it would include a newer kernel?

[thespad]

Nope, sadly not. The kernel version it ships with is what you're stuck with short of minor patches. This is a 916+ running DSM 7.2

$ uname -a
Linux NAS1 3.10.108 #64561 SMP Fri May 19 01:32:53 CST 2023 x86_64 GNU/Linux synology_braswell_916+

[squirtbrnr]

Oh that stinks. Yeah I just checked and I’m at 3.10.105. Oh well. Thanks for clarifying and explaining this to me.

[github-actions[bot]]

This issue is locked due to inactivity