You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am developing web services and testing them running in docker containers, which, in development mode, have my source directory mounted as volume and are installed in (strict) editable way.
As such, my source tree is mounted in editable way twice:
from the host (for interactive work, to allow my editor to infer types, etc)
from the docker container (to run the service)
The fact that the same build directory is used in two fundamentally different environment, by two different unix users, easily cause conflicts (a build in the container results in files owned by root in the host, and various other glitches).
Is there the possibility to move the build directory elsewhere? It doesn't seem from the docs and from pip -h and pip install -h.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am developing web services and testing them running in docker containers, which, in development mode, have my source directory mounted as volume and are installed in (strict) editable way.
As such, my source tree is mounted in editable way twice:
The fact that the same
build
directory is used in two fundamentally different environment, by two different unix users, easily cause conflicts (a build in the container results in files owned by root in the host, and various other glitches).Is there the possibility to move the
build
directory elsewhere? It doesn't seem from the docs and frompip -h
andpip install -h
.Beta Was this translation helpful? Give feedback.
All reactions