Skip to content

fix: Correct file paths in Dockerfile for backend requirements and code#480

Open
VishalSh-Microsoft wants to merge 1 commit into
microsoft:mainfrom
VishalSh-Microsoft:psl-pipelinefix-vs
Open

fix: Correct file paths in Dockerfile for backend requirements and code#480
VishalSh-Microsoft wants to merge 1 commit into
microsoft:mainfrom
VishalSh-Microsoft:psl-pipelinefix-vs

Conversation

@VishalSh-Microsoft

Copy link
Copy Markdown
Contributor

Purpose

This pull request updates the Docker build context for the backend service to use the correct relative paths when copying files into the Docker image. This ensures that the Docker build process works as expected when building from the repository root.

  • Docker build context correction:
    • Updated the COPY commands in docker/Backend.Dockerfile to use src/backend/requirements.txt and src/backend/ instead of ../src/backend/requirements.txt and ../src/backend/. This fixes file path issues during Docker image build.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request fixes the backend Docker image build by updating COPY paths in docker/Backend.Dockerfile to be correct when building with the repository root as the Docker build context (as used by GitHub Actions and documented docker build ... . commands).

Changes:

  • Update COPY for requirements.txt to src/backend/requirements.txt.
  • Update COPY for backend source to src/backend/.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants