🐛 Bug Report: ghcr.io/novuhq/novu/web:2.1.0 docker container STATUS (unhealthy) - curl: not found

[Aaron-Ritter]

📜 Description

community docker specifies a healthcheck with curl, but curl is not present in the ghcr.io/novuhq/novu/web:2.1.0 image

novu/docker/community/docker-compose.yml

Lines 159 to 185 in fd3cff6

	web:
	image: 'ghcr.io/novuhq/novu/web:2.1.0'
	depends_on:
	- api
	- worker
	container_name: web
	restart: unless-stopped
	logging:
	driver: 'json-file'
	options:
	max-size: '50m'
	max-file: '5'
	environment:
	REACT_APP_API_URL: ${API_ROOT_URL}
	REACT_APP_ENVIRONMENT: ${NODE_ENV}
	REACT_APP_WIDGET_EMBED_PATH: ${WIDGET_EMBED_PATH}
	REACT_APP_IS_SELF_HOSTED: 'true'
	REACT_APP_WS_URL: ${REACT_APP_WS_URL}
	ports:
	- 4200:4200
	command: ['/bin/sh', '-c', 'pnpm run envsetup:docker && pnpm run start:static:build']
	healthcheck:
	test: ['CMD-SHELL', 'curl --silent --fail http://localhost:4200 || exit 1']
	interval: 30s
	timeout: 10s
	retries: 3
	start_period: 10s

👟 Reproduction steps

1. run the community docker compose
2. open the shell of the web container
3. run curl

👍 Expected behavior

have curl installed and therefore have a successful test

👎 Actual Behavior with Screenshots

NAME                                     IMAGE                           COMMAND                  SERVICE   CREATED         STATUS                     PORTS
novu-web-1   ghcr.io/novuhq/novu/web:2.1.0   "docker-entrypoint.s…"   web       2 minutes ago   Up 2 minutes (unhealthy)   0.0.0.0:4200->4200/tcp, :::4200->4200/tcp

Novu version

Novu Community 2.1.0

npm version

No response

node version

No response

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

Yes I am willing to submit a PR!

[linear]

NV-5160 🐛 Bug Report: ghcr.io/novuhq/novu/web:2.1.0 docker container STATUS (unhealthy) - curl: not found

[youngbloodk]

Facing this same issue

[Aaron-Ritter]

Hi @jainpawan21 I agree that the unhealthy status is gone with this change. But I disagree on removing the checks rather than fixing them from an operational perspective.

Do you prefer for me to open a new issue instead of reopening this one? And referencing a possible solution in #7953