Zappa update fails with "import pip" command

[iwitaly]

I use Gitlab CI for updating my Zappa app with the following script.

  - export PIPENV_VENV_IN_PROJECT=true
  - pip install pipenv
  - pipenv install
  - export VIRTUAL_ENV=.venv/
  - export AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID_DEV
  - export AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY_DEV
  - export ENVIRONMENT=dev
  - pipenv run python manage.py migrate --settings=admin_dashboard.settings.dev
  - pipenv run zappa update dev

I also use lambci/lambda:build-python3.6 as a base image.

Until today all updates were good, but today I've got this error

What could that mean?

[Miserlou]

What changed in your system today? There was no new Zappa version..

…

On Sat, Mar 17, 2018 at 1:47 PM, Vitaly Davydov ***@***.***> wrote: I use Gitlab CI for updating my Zappa app with the following script. - export PIPENV_VENV_IN_PROJECT=true - pip install pipenv - pipenv install - export VIRTUAL_ENV=.venv/ - export AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID_DEV - export AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY_DEV - export ENVIRONMENT=dev - pipenv run python manage.py migrate --settings=admin_dashboard.settings.dev - pipenv run zappa update dev I also use lambci/lambda:build-python3.6 as a base image. Until today all updates were good, but today I've got this error [image: image] <https://user-images.githubusercontent.com/2273226/37558391-5e41fc94-2a24-11e8-9fdc-5884445e829a.png> What could that mean? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1446>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIi0woikAJbN0tpakxbv4X0KMIhYOCVks5tfUwzgaJpZM4Su5X5> .

[bmyrtil]

Good its not just me... Not sure what happened but this is no longer working for me as well. Worked last night. Really strange.

[iwitaly]

Nothing has changed from my side, I use the same Docker image and the same dependency file.
BTW on my local machine, everything works great.

[bmyrtil]

Same here, I literally just redeployed my application and start receiving this error.

I tested with library/python:3.6.4-alpine3.7 & frolvlad/alpine-python3 and received the same error as @iwitaly

[lampslave]

Do you have RUN pip install --upgrade pip wheel in your dockerfile? pip 9.0.2 was released today, I guess it may be broken.

[bmyrtil]

Hmmm good catch. WIll try downgrading.

[iwitaly]

@lampslave I do use lambci/lambda:build-python3.6 image without any modification. What do you suggest?

[bmyrtil]

Yup running "pip install pip==9.0.1" fixed my issue. Looks like something is up with 9.0.2

[lampslave]

@iwitaly Try to add RUN pip install --upgrade "pip==9.0.1" into your dockerfile.

[Miserlou]

Reported upstream.

[lampslave]

It seems that new setuptools also can break builds, if you found some problems try to freeze it too: "setuptools<39.0".

[iwitaly]

Do you know how to make it work with pipenv? Locking pipenv install pip=9.0.1 doesn't fix that error. I've switched to plain pip install -r requirements.txt but it's not good.