pipenv lock --requirements --no-hashes outputs hashes

I was trying to run pipenv in a Dockerfile and in order to install the deps globally I use this code:

ADD Pipfile /src/Pipfile
ADD Pipfile.lock /src/Pipfile.lock
RUN pipenv lock --requirements --no-hashes > /tmp/requirements.txt
RUN pip install -r /tmp/requirements.txt

since I’m developing on a mac the hashes will be different, so I’m using the --no-hashes option. Unfortunately this still outputs the hashes when using --requirements.

Is this the intended behaviour? If so how I can properly use pipenv in a Dockerfile? I don’t really need a virtualenv in this case

[nateprewitt]

Alright, we’re all tidied up with 86ef9b8. I’m going to wait a few days to cut the hotfix since this isn’t in the critical path. That will give some time for any other bugs in 3.5.4 to float in and hopefully get wrapped up.

Thanks again @patrick91! Glad you’ve got things working now.

[nateprewitt]

Hey @patrick91, thanks for spotting this! It looks like --no-hashes works as expected with pipenv lock --requirements --no-hashes when the Pipfile.lock doesn’t exist but not when it does. I’ll try to get this patched this morning.

For the time being, I would suggest removing the ADD Pipfile.lock /src/Pipfile.lock requirement from your Dockerfile for now and things should work as expected.