Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setup_venv.sh fails to install Pipfile.lock dependencies on AWS Ubuntu 22.04 and 20.04 Instances #234

Open
trevorrobertsjr opened this issue Jul 20, 2023 · 2 comments

Comments

@trevorrobertsjr
Copy link

Describe the bug
setup_venv.sh fails to install Pipfile.lock dependencies on AWS Ubuntu 22.04 and 20.04 Instances

To Reproduce
Steps to reproduce the behavior:

  1. Install Pulumi and perform pulumi login
  2. Install AWS CLI
  3. Install suggested Debian packages from getting_started
  4. Clone repo with recurse-submodules flag
  5. Run bash ./bin/setup_venv.sh

Expected behavior
I expect the PIP package installation to succeed with no issues.

Your environment

  • Version of the repo - aa8ee93 Whatever is current as of 7/20/2023
  • Version of KIC - ? Whatever is current as of 7/20/2023
  • Version of infrastructure tooling (e.g. Pulumi) - 3.75.0
  • Version of executing environment (e.g. Python, node) - 3.9.17
  • OS and distribution - Ubuntu 20.04 and 22.04
  • Details about containerization or virtualization environment - AWS instances

Additional context
Add any other context about the problem here. Any log files you want to share. - Happy to share logs if someone can comment on how to generate them. I copied the error messages to a Gist

@4141done
Copy link
Contributor

Hello, thanks for reporting this and I'm sorry you're not having a smooth experience. I ran into a similar issue recently and I am still trying to diagnose the exact error python is having.

However, I do have a branch that I am using to test updates to the Pulumi libraries that is working for me in the same environment that I encountered this error before. Would you mind giving that a try and see if it solves your error?

#233

@k7k0
Copy link

k7k0 commented May 24, 2024

@4141done I was suffering a similar issue on MacOS, switched to that PR branch and the setup worked 👍

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

No branches or pull requests

3 participants