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

Health check for container #336

Open
toni-rib-skydio opened this issue Feb 5, 2025 · 2 comments
Open

Health check for container #336

toni-rib-skydio opened this issue Feb 5, 2025 · 2 comments

Comments

@toni-rib-skydio
Copy link

We have a service that uses sish as part of many services in a docker-compose.yml. All of the services minus sish expose some kind of health check we can use to ensure it's up and responding. Would it be possible to add something like that?

@antoniomika
Copy link
Owner

Just getting back to this:

Yep, that should be doable. Healthchecking sish's root for a 302 or a 404 doesn't work for you?

@toni-rib-skydio
Copy link
Author

So the issue that I've been running into is that with the entrypoint to the container being /app/app, it isn't exposing anything like wget, curl, even sh that I can use as part of a kubernetes health check in our docker-compose.yml to check against the root. Other things we are running like prometheus have this exposed so I can add something like this, where fast_healthcheck just defines the interval, timeout, retries, etc.

    healthcheck:
      test: wget --spider -q http://localhost:9090/-/healthy || exit 1
      <<: *fast_healthcheck

So far I haven't been able to get anything to work with sish that would be somewhat of an equivalent just to say "yes this container is running and healthy."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants