fix(docker): fixes the health check wget

[tankerkiller125]

What type of PR is this?

• bug

What this PR does / why we need it:

Fixes the docker health check, we can't use wget --spider because the API does not accept the correct HTTP HEAD method

Which issue(s) this PR fixes:

Fixes #103

Summary by CodeRabbit

• Chores
  • Updated health check commands in Dockerfiles to use wget with the -O - option for improved service status checks.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates in the Dockerfile and Dockerfile.rootless address the health check failures reported in version v0.12.0 by modifying the HEALTHCHECK command. The updated wget command now includes the -O - option to output the response to stdout, improving the interaction with the health status endpoint.

Changes

Files	Change Summary
Dockerfile	HEALTHCHECK command updated to use wget -O - to improve health status diagnoses.
Dockerfile.rootless	Similar HEALTHCHECK command update to leverage wget -O - for stdout output.

Sequence Diagram(s)

Changes do not involve new features or control flow modifications that warrant sequence diagrams.

Assessment against linked issues

Objective (Issue #103)	Addressed	Explanation
Modify the HEALTHCHECK command to ensure wget correctly checks endpoint's health	✅
Ensure wget correctly outputs response to stdout	✅

Poem

In the Docker realm, changes brew,
Health checks no longer misconstrue.
wget now with -O - command,
Health status at your command.
Containers sail smooth as planned. ⛵

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6fcf996 and 641b8c1.

Files selected for processing (2)

• Dockerfile (1 hunks)
• Dockerfile.rootless (1 hunks)

Files skipped from review due to trivial changes (1)

• Dockerfile

Additional comments not posted (1)

Dockerfile.rootless (1)

57-57: Sir, ensure the health check command functions as intended.

The modification to include -O - in the wget command directs the output to stdout, which might resolve the issue with the health check. This change aligns with the PR objectives to correct the health check process. However, verify that this change effectively resolves the issue in various environments.