How to pass healthchecks with a docker container that has no routes exposed?

[tomcru]

I have the issue that I want to run a Docker container that includes cron jobs, but it has no routes exposed that I could be using for Healthchecks. I am using a Dockerfile. Is there a way to disable URL based healthchecks?

[sisou]

The app config has a section called 'Healthchecks'. It let's you disable them.

[tomcru]

This is not the case when you are using a Dockerfile.

[seb-L8L]

Same issue here.
@tomcru did you find a solution?

[tomcru]

I ended up using docker compose, not the Dockerfile. Docker compose has no healthchecks by default.

[seb-L8L]

Thanks! I guess we'll have to do the same.

@andrasbacsai any input on that matter?

[andrasbacsai]

Did you try this? You can add healthcheck in the dockerfile that will execute "exit 0", so it always be true.

[seb-L8L]

Yes I did.
Here is my Dockerfile:

FROM alpine:latest

RUN apk upgrade --no-cache
RUN apk add --no-cache ca-certificates
RUN apk add s3cmd

HEALTHCHECK CMD exit 0

CMD ["sh"]

and the result log I got:

Starting deployment of lesoctetslibres-website-s3cmd to l8l-coolify.
Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.1.
----------------------------------------
Building docker image started.
To check the current progress, click on Show Debug Logs.
Building docker image completed.
----------------------------------------
Rolling update started.
New container started.
Custom healthcheck found, skipping default healthcheck.
Waiting for healthcheck to pass on the new container.
Healthcheck URL (inside the container): GET: http://localhost:80/
Waiting for the start period (5 seconds) before starting healthcheck.
Attempt 1 of 10 | Healthcheck status: "unhealthy"
----------------------------------------
Container logs:
----------------------------------------
Removing old containers.
----------------------------------------
WARNING: Dockerfile or Docker Image based deployment detected. The healthcheck needs a curl or wget command to check the health of the application. Please make sure that it is available in the image or turn off healthcheck on Coolify's UI.
----------------------------------------
New container is not healthy, rolling back to the old container.
Rolling update completed.

It looks as if the healthcheck is checked against route http://localhost:80 even though I have no healthcheck enabled on this resource.
(I'm on the Cloud version v4.0.0-beta.347)