Update Dockerfile

[shivakumarkadli4272]

Summary by CodeRabbit

• Chores
  • Updated the port exposed by the container from 8000 to 8100.

[coderabbitai]

Walkthrough

The changes involve a modification to the Dockerfile, specifically updating the port that the container exposes. The previous port 8000 has been changed to port 8100, with no other alterations to functionality, logic, or control flow.

Changes

File	Change Summary
Dockerfile	Updated exposed port from 8000 to 8100

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant DockerContainer

    Client->>DockerContainer: Request on port 8100
    DockerContainer-->>Client: Response

Loading

🐰 "In the garden where we play,
The port has changed, hip-hip-hooray!
From eight to ten, we bounce about,
With joyful hops and a happy shout!
Let's celebrate this little win,
A new port's here, let the fun begin!" 🥕

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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

🧹 Outside diff range comments (2)

Dockerfile (2)

Line range hint 1-1: Security: Update the Node.js base image version

The current base image node:12.2.0-alpine is significantly outdated and has reached end-of-life (April 2022), potentially exposing your application to security vulnerabilities. Consider upgrading to an actively maintained LTS version.

-FROM node:12.2.0-alpine
+FROM node:20-alpine

🧰 Tools

🪛 Hadolint (2.12.0)

[info] 12-12: Multiple consecutive RUN instructions. Consider consolidation.

(DL3059)

---

Line range hint 9-10: Consider moving tests outside of the Dockerfile

Running tests during image building (RUN npm run test) can lead to several issues:

1. Failed tests will prevent deployment of the image
2. Tests might require additional dependencies or services
3. Increases build time and image size

Consider running tests in your CI/CD pipeline instead.

#Install the dependecies
RUN npm install
-RUN npm run test

🧰 Tools

🪛 Hadolint (2.12.0)

[info] 12-12: Multiple consecutive RUN instructions. Consider consolidation.

(DL3059)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 2ca076c and 3106787.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

🔇 Additional comments (1)

Dockerfile (1)

13-13: Verify port change coordination across the application

While changing the exposed port from 8000 to 8100 is straightforward, we should ensure this change is coordinated with other configurations.