Git submodules in docker

pipenv, version 11.10.0

I have a submodule ./dep1 in my git repo and am adding it to pipenv via pipenv install -e dep1, which works just fine and adds the line

"abc123" = {path = "./dep1", editable = true}

to my Pipfile. Then I use a Dockerfile as follows:

FROM kennethreitz/pipenv
COPY ./app /app
COPY ./dep1 /app/dep1
CMD python3 start.py

where I added the third line, so the submodule is available in the WORKDIR. However, upon docker build I am getting the following error

+ pipenv install --deploy --system
Installing -e ./dep1…

Error:  An error occurred while installing -e ./dep1!
./dep1 should either be a path to a local project or a VCS url beginning with svn+, git+, hg+, or bzr+

This is unexpected, since ./dep1 is a path to a local project, relative to the WORKDIR in the docker image with the Pipfile, which is /app. Am I missing something or is this a bug?

[erinxocon]

I don’t think my solution is the proper way, I’m working on another, but essentially, when the pipfile references the local package, the lockfile becomes different for each platform, your host machine and the docker instance since they are in difference places. pipenv install creates a virtualenv, and relocks the pipfile and then pipenv install --deploy --system uses that new updated lockfile for the install. So we are essentially creating a virtualenv when it’s not needed to sync lockfiles after you install the new local dep…I’m looking into a better Dockerfile solution now.

[techalchemy]

(For the record it was much simpler than that, thankfully)