Devcontainer: Investigate the UX around venv activation and fix issue with poetry running in other directories

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor - P4
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Test Infrastructure
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      From kaloian.manassiev@mongodb.com 

      Starting bash in the container and immediatelly running activate and poetry sync is kind of a bad UX and on top of that it prints some cryptic error:

      [kaloianm@M-Q97VL4W3FX:~]$ docker exec -it fe392e34e821cce1a582640743c691a5d3ddcfdd7ef77d6983278627358a4ecd /usr/bin/bash
      Using '/workspaces/mongo/python3-venv/bin/python3' based on VIRTUAL_ENV=/workspaces/mongo/python3-venv
      env PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring /workspaces/mongo/python3-venv/bin/python3 -m poetry sync --no-root

      Poetry could not find a pyproject.toml file in / or its parents

            Assignee:
            Eric Lavigne
            Reporter:
            Eric Lavigne
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: