Ben Smith

I'm hitting this too. Runs perfectly locally (OSX) but when using Codeship and the following Dockerfile: ``` FROM docker:dind RUN apk add --update \ nodejs \ python3 \ py-pip \...

I've been playing with this a bit more and there's definitely something about running the pip install through docker, from within another docker. I guess one way to get around...

So this Dockerfile seems to be working, obviously dockerizePip has to be false: ``` FROM lambci/lambda:build-nodejs6.10 ENV AWS_DEFAULT_REGION eu-west-1 \ PYTHONPATH=/var/runtime \ PKG_CONFIG_PATH=/var/lang/lib/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig RUN curl https://lambci.s3.amazonaws.com/fs/python3.6.tgz | tar -xz -C...

@tgensol FWIW it's Codeship, not CircleCI. On Codeship Pro, the install / deploy process is itself run in a docker image built using that Dockerfile (with dockerizePip set to false).