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

pip install -r adf-build/requirements.txt -q. Reason: exit status 1 #441

Closed
stefl3n opened this issue Feb 22, 2022 · 3 comments
Closed

pip install -r adf-build/requirements.txt -q. Reason: exit status 1 #441

stefl3n opened this issue Feb 22, 2022 · 3 comments
Milestone

Comments

@stefl3n
Copy link

stefl3n commented Feb 22, 2022

[Container] 2022/02/22 15:23:27 Running command pip install -r adf-build/requirements.txt -q
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-c4j8yl00/MarkupSafe/
You are using pip version 18.1, however version 22.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

[Container] 2022/02/22 15:23:45 Command did not exit successfully pip install -r adf-build/requirements.txt -q exit status 1
[Container] 2022/02/22 15:23:45 Phase complete: INSTALL State: FAILED
[Container] 2022/02/22 15:23:45 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: pip install -r adf-build/requirements.txt -q. Reason: exit status 1

@at7925
Copy link
Contributor

at7925 commented Feb 23, 2022

What version of python do you use during the build?

The same error also start happening on 22-feb-2022 for some of my old pipelines because of outdated pip/python from legacy build image aws/codebuild/python:3.7.1

simple solution: add an explicit image statement to the build section of the pipeline definition, e.q.:

      build:
        provider: codebuild
        properties:
          image: "STANDARD_5_0"

likely "STANDARD_4_0" and "AMAZON_LINUX_2" will work as well (have not verified)

@stefl3n
Copy link
Author

stefl3n commented Feb 23, 2022

Hi,
first of all thanks for your suggestion.

I solved the issue adding this command "pip install --upgrade pip" in the buildspec.yml file as suggested here: #440

Let me know if there's something wrong with this solution!

Thanks a lot.

@sbkok sbkok added this to the v3.2.0 milestone Sep 26, 2022
@sbkok
Copy link
Collaborator

sbkok commented Jan 24, 2023

Thank you for your patience. I am happy to inform you that this issue has been resolved in our latest release v3.2.0 just now.
I'm hereby closing this issue. Please open a new issue if you are experiencing any issues with the latest release.

@sbkok sbkok closed this as completed Jan 24, 2023
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