Update dev container

[bamurtaugh]

Fixes #6172

As described in #6172, I'd love to help update the dev container in this project.

Summary of changes:

• Dev container now builds (the current container in this repo won't build for me)
• Dockerfile updates
  • Update image to our currently-maintained Python image (mcr.microsoft.com/devcontainers/python) rather than the deprecated image from vscode-dev-containers
  • Move Dockerfile to root of repo - in order for COPY to work properly, it needs the files (in this case, pyproject.toml and poetry.toml) in the same directory
• devcontainer.json updates
  • Removed customizations and remoteUser since they should be covered by the updated image in the Dockerfile
  • Update comments
• Update docker-compose.yaml to properly point to updated Dockerfile
• Add a .gitattributes to avoid line ending conversions, which can result in hundreds of pending changes (info)
• Add a README in the .devcontainer folder and info on the dev container in the contributing.md

Outstanding questions:

• Is it expected for poetry install to take some time? It takes about 30 minutes for this dev container to finish building in a Codespace, but a user should only have to experience this once. Through some online investigation, this doesn't seem unusual
• Versions of poetry newer than 1.3.2 failed every time - based on some of the guidance in contributing.md and other online resources, it seemed changing poetry versions might be a good solution. 1.3.2 is from Jan 2023

Who can review?

Tag maintainers/contributors who might be interested: @vowelparrot

I was able to run through the various make commands mentioned in contributing.md successfully with this updated setup, and please let me know if there are questions or other tests I can help with to ensure everything is running well. Thanks so much!

[samruddhikhandale]

FYI, we will soon release a new major version of python in order to support debian:bookworm
devcontainers/images#622

I'd recommend switching once it's live to continue receiving security patches

[vowelparrot]

Thanks for letting us know, @samruddhikhandale !

[vowelparrot]

Versions of poetry newer than 1.3.2 failed every time - based on some of the guidance in contributing.md and other online resources, it seemed changing poetry versions might be a good solution. 1.3.2 is from Jan 2023

cc @eyurtsev FYI

[vowelparrot]

Is it expected for poetry install to take some time? It takes about 30 minutes for this dev container to finish building in a Codespace, but a user should only have to experience this once. Through some online investigation, this doesn't seem unusual

Are there any logs you would be able to share on this one? It's surprising that it would take 30 minutes unless we're installing ALL the optional dependencies. The list of actual requirements isn't that large

[vowelparrot]

What's the fastest way to build the dev container and codespace on your branch? I can look into it tomorrow morning if I get to it before you see this.

[bamurtaugh]

Thanks so much for the review @samruddhikhandale!

@vowelparrot you should be able to use the Code dropdown at the top of this PR:

Or from my fork: https://github.com/bamurtaugh/langchain/tree/bamurtaugh/dev-container.

It'd be awesome to have you try it out and see if there's something apparent from your perspective that'd be causing it to hang.

[vowelparrot]

We probably don't need to install all of "--with dev,test,docs" on container creation (unless it's really terrible to add additional dependencies). I'd remove the "docs" group and see how long it takes then

[bamurtaugh]

I'd remove the "docs" group and see how long it takes then

Thanks for the recommendation @vowelparrot! I'm trying that now. Still going and it's been about 8 minutes, so still feels longer than expected?

Edit: Have to step away for a bit, but it's still building at the 20-minute mark. 🤔 Does it take this long for other folks to generally run a poetry install?