-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System installation for docker containers #5340
Comments
@nikoskaramo use |
@nikoskaramo The issue appears to be that you are getting a newer version of Python in your docker deploy. I got this same error trying to install
|
FWIW I get the same error on |
@matteius I receive the same error for all dependencies beginning with pipenv-2022.9.4 (also pipenv-2022.9.8) but not using --system. The last successful build was on pipenv-2022.8.30 pipenv install --dev --deploy
Python 3.10 |
@matteius the setup.py error message received on #5332 or #5319 does not appear.
|
…2022.8.31. Pin 2022.8.30 for now. When resolution exists on pypa/pipenv#5340, unpin pipenv.
…2022.8.31. Pin 2022.8.30 for now. When resolution exists on pypa/pipenv#5340, unpin pipenv. (#1743)
@jkueloc I just tried the
|
I got the following error with the
|
It worked though if I did |
@matteius --system was not used. |
@jkueloc I cannot reproduce, even with the lock file you have checked in the
|
@matteius It's running in Jenkins which kicks off the build_containers.sh script |
@jkueloc It looks like the Dockerfile itself isn't pinned on pipenv and builds fine, but that the build_contianers.sh script runs pipenv on Jenkins directly before kicking off the Docker build: https://github.com/LibraryOfCongress/concordia/blob/main/build_containers.sh#L22 For further debugging, are you able to verify the python version of python that jenkins is using to create the virtualenv?: https://github.com/LibraryOfCongress/concordia/blob/main/build_containers.sh#L14-L15 Alternatively, what if you let pipenv create the virtualenv? You can have it create it in the .venv directory of the project with environment variable |
@jkueloc Actually I just figured out its the dev dependencies that are having the issue and not the default -- let me dig a littler deeper now that I can reproduce this. |
@jkueloc The problem is definitely with the pre-creation of the virtualenv -- not sure why though.
|
@jkueloc It seems with the
|
@jkueloc Short answer, you can
|
* CONCD-167 pipenv=2022.9.4 and laster are failing. Issue starts with v2022.8.31. Pin 2022.8.30 for now. When resolution exists on pypa/pipenv#5340, unpin pipenv. * add --system for Jenkins test
* CONCD-167 pipenv=2022.9.4 and laster are failing. Issue starts with v2022.8.31. Pin 2022.8.30 for now. When resolution exists on pypa/pipenv#5340, unpin pipenv. * add --system for Jenkins test * remove pin to test Jenkins
@matteius Why sync versus install? Thank you for your quick detailed responses and working to recreate the issue. |
* CONCD-167 pipenv=2022.9.4 and laster are failing. Issue starts with v2022.8.31. Pin 2022.8.30 for now. When resolution exists on pypa/pipenv#5340, unpin pipenv. * add --system for Jenkins test * remove pin to test Jenkins * pre-install packaging
@jkueloc No real reason, I am just used to doing that, but it doesn't validate the meta hash of the lockfile the way |
Issue description
When including
--system
option to install packages on the system level inside a Docker image (RUN pipenv install --dev --system --ignore-pipfile
), installation of all packages fail with an error similar to the one below:Removing the
--system
option installs the packages in a virtual environment. However, this option won't work in our Docker image.Pipenv version 2022.8.5 works with no issues
Expected result
To install all packages using
--system
option.Actual result
Steps to replicate
RUN pipenv install --dev --system --ignore-pipfile
The text was updated successfully, but these errors were encountered: