Docker container reporting unhealthy status
bucketsadmin opened this issue · comments
Describe the Bug
With the newest release, the internal healthcheck for the viewtube docker container is showing a constant unhealthy status. The application itself runs fine and when publishing the ports to the host viewtube is fully accessibly and running properly.
However, due to the unhealthy status of the container any attached labels do not get published to the docker service. This is impacting the ability for services such as Traefik to properly route traffic to the container.
Error being reported by the internal healthcheck:
http://localhost:8066/: Remote file does not exist -- broken link!!!
Whatever values are expected to be returned in the healthcheck are not being presented by the internal webserver.
Steps to Reproduce the Bug
Deployment via docker compose using the container from docker hub mauriceo/viewtube:latest.
Expected Behaviour
Healthcheck completes successfully
Screenshot/Screen recording
internal healthcheck report (portainer)
Device Info
- Device: Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
- Container release: 0.16.1
- OS: Ubuntu 22.04.4 LTS
- Browser: any
- Version: any
Additional Context
Deploying the compose file via portainer and via docker compose up -d results in the same behavior on different Linux releases.