fix-connector-docker-build

[jasquat]

Run poetry install after copying in the current dir for connector-example.

Summary by CodeRabbit

• Chores
  • Improved readability of the Dockerfile by adjusting formatting for package installations and commands.
  • Added comments for clarity regarding the version of poetry used.
  • No changes to functionality; enhancements are primarily cosmetic.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes in the Dockerfile primarily involve modifications to the installation of packages and management of Python dependencies. The base image remains python:3.11.6-slim-bookworm, with the virtual environment set to /app/venv. Formatting adjustments have been made for readability in the RUN commands for package installations, while the functionality remains unchanged. Additionally, a comment regarding the pinned version of poetry to 1.6.1 has been included, and the overall structure of the Dockerfile has been refined for clarity without altering its operational behavior.

Changes

File	Change Summary
connector-proxy-demo/Dockerfile	- Updated formatting of package installation commands for better readability.
	- Added comment regarding pinning poetry version to 1.6.1 to avoid PEP 517 build issues.
	- Reformatted apt-get update and installation commands for clarity without functional changes.

Possibly related PRs

• Try to head off file ownership issues #2096: This PR modifies the Dockerfile to change the version of Poetry to 1.6.1, which is also mentioned in the main PR, indicating a shared focus on managing Python dependencies.
• Editable dev container for connector proxy demo #2097: This PR includes updates to the Makefile and Docker Compose configuration for the connector proxy demo, which is directly related to the Dockerfile changes in the main PR, as both are part of the same project and involve dependency management and container setup.

---

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.

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.