[GH-ISSUE #82] Docker container healthcheck #52

Closed
opened 2026-02-27 10:15:31 +03:00 by kerem · 5 comments
Owner

Originally created by @ilgigante77 on GitHub (Nov 28, 2024).
Original GitHub issue: https://github.com/matze/wastebin/issues/82

Is there a way to get a docker healthckeck via some internal command?

Originally created by @ilgigante77 on GitHub (Nov 28, 2024). Original GitHub issue: https://github.com/matze/wastebin/issues/82 Is there a way to get a docker healthckeck via some internal command?
kerem closed this issue 2026-02-27 10:15:31 +03:00
Author
Owner

@matze commented on GitHub (Jan 14, 2025):

What exactly do you mean? If the service is still up and running? I'd say GET / and you are golden.

<!-- gh-comment-id:2589703297 --> @matze commented on GitHub (Jan 14, 2025): What exactly do you mean? If the service is still up and running? I'd say `GET /` and you are golden.
Author
Owner

@ilgigante77 commented on GitHub (Jan 19, 2025):

this;

healthcheck:
test: "wget --no-verbose --tries=1 --spider http://127.0.0.1:xxxx || exit 1"
interval: 1m30s
timeout: 10s
retries: 3
start_period: 5s

or implementing this in Dockerfile:

HEALTHCHECK [OPTIONS] CMD

or implementing the /health endpoint...

its the container that checks itself internally, not an external call.

<!-- gh-comment-id:2600756789 --> @ilgigante77 commented on GitHub (Jan 19, 2025): this; healthcheck: test: "wget --no-verbose --tries=1 --spider http://127.0.0.1:xxxx || exit 1" interval: 1m30s timeout: 10s retries: 3 start_period: 5s or implementing this in Dockerfile: HEALTHCHECK [OPTIONS] CMD <command> or implementing the /health endpoint... its the container that checks itself internally, not an external call.
Author
Owner

@matze commented on GitHub (Jan 20, 2025):

I am not convinced that supervision functionality (your example is definitely more than a check) should be part of the base image. If you need this, you can use a custom Docker image based on wastebin:latest and add this. I personally use systemd for proper restarts and checks and don't want to be interfered by this.

<!-- gh-comment-id:2602288088 --> @matze commented on GitHub (Jan 20, 2025): I am not convinced that supervision functionality (your example is definitely more than a check) should be part of the base image. If you need this, you can use a custom Docker image based on `wastebin:latest` and add this. I personally use systemd for proper restarts and checks and don't want to be interfered by this.
Author
Owner

@ilgigante77 commented on GitHub (Jan 20, 2025):

Ok, but this is a standard behaviour of docker. I will create my own image

Il lun 20 gen 2025, 13:23 Matthias Vogelgesang @.***>
ha scritto:

I am not convinced that supervision functionality (your example is
definitely more than a check) should be part of the base image. If you need
this, you can use a custom Docker image based on wastebin:latest and add
this. I personally use systemd for proper restarts and checks and don't
want to be interfered by this.


Reply to this email directly, view it on GitHub
https://github.com/matze/wastebin/issues/82#issuecomment-2602288088, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKCQNHPSHLOYDP3NIVJ2JK32LTTFLAVCNFSM6AAAAABSU6CKUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBSGI4DQMBYHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:2602310035 --> @ilgigante77 commented on GitHub (Jan 20, 2025): Ok, but this is a standard behaviour of docker. I will create my own image Il lun 20 gen 2025, 13:23 Matthias Vogelgesang ***@***.***> ha scritto: > I am not convinced that supervision functionality (your example is > definitely more than a check) should be part of the base image. If you need > this, you can use a custom Docker image based on wastebin:latest and add > this. I personally use systemd for proper restarts and checks and don't > want to be interfered by this. > > — > Reply to this email directly, view it on GitHub > <https://github.com/matze/wastebin/issues/82#issuecomment-2602288088>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKCQNHPSHLOYDP3NIVJ2JK32LTTFLAVCNFSM6AAAAABSU6CKUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBSGI4DQMBYHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@matze commented on GitHub (Jan 20, 2025):

Sorry, I don't follow. How is container technology related to how things are run inside the container? Do you have some reading material?

<!-- gh-comment-id:2602337794 --> @matze commented on GitHub (Jan 20, 2025): Sorry, I don't follow. How is container technology related to how things are run inside the container? Do you have some reading material?
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/wastebin-matze#52
No description provided.