[GH-ISSUE #519] [BUG] unhealthy on docker - though healthy and working #337

Closed
opened 2026-02-25 20:35:29 +03:00 by kerem · 5 comments
Owner

Originally created by @sutidor on GitHub (Nov 2, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/519

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Install whoogle container
  2. see it being constantly unhealthy

Deployment Method

  • Heroku (one-click deploy)
  • Docker
  • run executable
  • pip/pipx
  • Other: [describe setup]

Version of Whoogle Search

  • Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
  • Version [version number]
  • Not sure

Additional context
There is no publicly exposed port, whoogle is reverse proxied. Going into whoogle container terminal and curl http://localhost:${EXPOSE_PORT}/healthz || exit 1 gives no return. curl -i and going to published url with browser gives me return code 200. How to fix?

Originally created by @sutidor on GitHub (Nov 2, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/519 **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Install whoogle container 2. see it being constantly unhealthy **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure **Additional context** There is no publicly exposed port, whoogle is reverse proxied. Going into whoogle container terminal and `curl http://localhost:${EXPOSE_PORT}/healthz || exit 1` gives no return. curl -i and going to published url with browser gives me return code 200. How to fix?
kerem 2026-02-25 20:35:29 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@benbusby commented on GitHub (Nov 7, 2021):

Hmmm, I'm not sure what the problem could be here. Could you run docker inspect --format "{{json .State.Health }}" whoogle-search | jq and share the results?

<!-- gh-comment-id:962661065 --> @benbusby commented on GitHub (Nov 7, 2021): Hmmm, I'm not sure what the problem could be here. Could you run `docker inspect --format "{{json .State.Health }}" whoogle-search | jq` and share the results?
Author
Owner

@sutidor commented on GitHub (Nov 8, 2021):

dont know how to jq on ubuntu but here the docker inspect --format "{{json .State.Health }}" whoogle-searchbit:
{"Status":"unhealthy","FailingStreak":1714,"Log":[{"Start":"2021-11-08T10:37:29.387401171+01:00","End":"2021-11-08T10:37:29.454545693+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:42:29.457327157+01:00","End":"2021-11-08T10:42:29.524791178+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:47:29.527064049+01:00","End":"2021-11-08T10:47:29.5934602+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:52:29.595778319+01:00","End":"2021-11-08T10:52:29.683696621+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:57:29.686125891+01:00","End":"2021-11-08T10:57:29.762943074+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"}]}
Interesting. When docker exec into container curl works but wget does not. Using image v0.6.0 sha256:e3473b7003866a1973ae2d26a71834199661777f3f4007859fc35b718e99ea0b

<!-- gh-comment-id:962991278 --> @sutidor commented on GitHub (Nov 8, 2021): dont know how to jq on ubuntu but here the `docker inspect --format "{{json .State.Health }}" whoogle-search`bit: ```{"Status":"unhealthy","FailingStreak":1714,"Log":[{"Start":"2021-11-08T10:37:29.387401171+01:00","End":"2021-11-08T10:37:29.454545693+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:42:29.457327157+01:00","End":"2021-11-08T10:42:29.524791178+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:47:29.527064049+01:00","End":"2021-11-08T10:47:29.5934602+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:52:29.595778319+01:00","End":"2021-11-08T10:52:29.683696621+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2021-11-08T10:57:29.686125891+01:00","End":"2021-11-08T10:57:29.762943074+01:00","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"}]}``` Interesting. When docker exec into container curl works but wget does not. Using image v0.6.0 sha256:e3473b7003866a1973ae2d26a71834199661777f3f4007859fc35b718e99ea0b
Author
Owner

@benbusby commented on GitHub (Nov 9, 2021):

Well that's odd...the Dockerfile uses curl and not wget for the healthcheck.

github.com/benbusby/whoogle-search@3f40a6c485/Dockerfile (L77-L78)

It's actually been that way since 0.5.0 (1fdf226802 ). Is it possible your Dockerfile is older than 0.6.0 due to changes that you've made locally? Either way somehow you've ended up with 0.6.0 code, but an old Dockerfile, which is strange.

<!-- gh-comment-id:964272881 --> @benbusby commented on GitHub (Nov 9, 2021): Well that's odd...the Dockerfile uses `curl` and not `wget` for the healthcheck. https://github.com/benbusby/whoogle-search/blob/3f40a6c485aa056d0ef5309d47966d4bcd1fd8a7/Dockerfile#L77-L78 It's actually been that way since 0.5.0 (1fdf226802d67445f7570b34a3323463e165770d ). Is it possible your Dockerfile is older than 0.6.0 due to changes that you've made locally? Either way somehow you've ended up with 0.6.0 code, but an old Dockerfile, which is strange.
Author
Owner

@sutidor commented on GitHub (Nov 11, 2021):

healthy!
I removed everything and started anew
Thank you for this amazing project as well as your support.

<!-- gh-comment-id:966316196 --> @sutidor commented on GitHub (Nov 11, 2021): healthy! I removed everything and started anew Thank you for this amazing project as well as your support.
Author
Owner

@benbusby commented on GitHub (Nov 12, 2021):

Awesome! Glad it's working now.

<!-- gh-comment-id:967222410 --> @benbusby commented on GitHub (Nov 12, 2021): Awesome! Glad it's working now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/whoogle-search#337
No description provided.