lyft / lyft/omnibot

healthcheck endpoint is not working outside container

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
87
Forks
16
PR merge metrics
No merged PRs in 30d

Description

My omnibot deployment is not working, I tried to setup locally using docker-compose and still the same.
One strange thing I noticed is, when I run curk -i -k http:0.0.0.0/healthcheck from inside container it returns 200/OK but from outside it returns 404.
Can you help me fix this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the request to /healthcheck from inside and outside the docker-compose deployment, then trace the container's published ports and HTTP routing. Done means the healthcheck responds 200/OK from outside the container as well as inside it.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, python
Domain
api, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.