Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navidrome 0.40 - unhealthy docker container on armv7 #773

Closed
0xERR0R opened this issue Feb 9, 2021 · 3 comments
Closed

Navidrome 0.40 - unhealthy docker container on armv7 #773

0xERR0R opened this issue Feb 9, 2021 · 3 comments

Comments

@0xERR0R
Copy link
Contributor

0xERR0R commented Feb 9, 2021

Navidrome 0.40 starts as "unhealthy" docker container. I run navidrome on Rasbperry pi 3 behind traefik and unhealthy state makes the container unreachable.
Message from docker inspect Connecting to localhost:4533 (127.0.0.1:4533)\nwriting to stdout\nwget: clock_gettime(MONOTONIC) failed\n
The problem is not a navidrome itself, it is caused by update to alpine 3.13 (which was released last month). See alpinelinux/docker-alpine#135

It looks like it is only arm7 issue.

As workaround, I suggest to bump alpine version in the docker file to 3.12

Workaround for affected users: add following to docker-compose.yml

healthcheck:
  disable: true
@deluan
Copy link
Member

deluan commented Feb 9, 2021

Thanks for letting me know!

Unfortunately I don't think locking the version to 3.12 and not getting future upgrades is a solution.... based on the linked issue, the real solution is to update the server: alpinelinux/docker-alpine#135 (comment)

For those having this issue, please upgrade your system as per linked instructions or disable the healthcheck as suggested above

Closing this now, but feel free to reopen if you have other concerns

@deluan deluan closed this as completed Feb 9, 2021
@ilPeo
Copy link

ilPeo commented Feb 9, 2021 via email

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants