Question 187814 in Amazon Web Sevices Question posted in
The official Amazon Web Services documentation can be found here.

Amazon web services – Amplify build fails with [Error: Command failed with exit code 1: pipenv –venv]

I am building a website with AWS Amplify. This website uses amongst other things, several Python Lambda functions.

Today, when building I get the following error message :

🛑 Received error [Error: Command failed with exit code 1: pipenv --venv
No virtualenv has been created for this project(PATH_TO_ONE_OF_THE_FUNCTIONS) yet!
Aborted!] running command [pipenv --venv]

(I have replaced the path with PATH_TO_ONE_OF_THE_FUNCTIONS because every time I try to redeploy the build it gives this error with a different function)

I have not changed anything in the backend since my last build (which was successful), I have only been working on the frontend.

I have no idea what is causing pipenv –venv to fail.

Here is my amplify.yml file :

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci --force
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
backend:
  phases:
    build:
      commands:
        - update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.9
        - /usr/local/bin/python3.9 -m pip install --upgrade pip
        - /usr/local/bin/pip3.9 install --user pipenv==2022.4.8
        - amplifyPush --simple

I am using the latest version of the Amplify CLI (12.1.0) on Mac. When running amplify push on my command prompt it doesn’t raise any errors.

Tags:

2

Answers


  1. 0

    Can you change your backend command like this and try again?

    backend:
  phases:
    build:
      commands:
        - update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.9 11
        - /usr/local/bin/pip3.9 install --user pipenv==2022.4.8
        - amplifyPush --simple
    Login or Signup to reply.
  2. 0

    I had the same issue. For me the solution didn’t worked and I resolved it by a solution I don’t think is optimal. In my amplify.yml I manually go create the pipenv for the functions adding that line for each function before the amplifyPush –simple.

    - export CUR_PWD=$(pwd)
- cd $CUR_PWD/amplify/backend/function/<FunctionFolder> && pipenv install --python /usr/local/bin/python3.9 && cd $CUR_PWD
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search