Skip to content

Pipenv gets blocked while running with Docker in Gitlab #3575

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

Closed
Peque opened this issue Mar 4, 2019 · 3 comments
Closed

Pipenv gets blocked while running with Docker in Gitlab #3575

Peque opened this issue Mar 4, 2019 · 3 comments

Comments

@Peque
Copy link

Peque commented Mar 4, 2019

I created this simple project in Gitlab:

https://gitlab.com/PequeX/deleteme

With a Pipfile that installs only a couple of packages:

[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]
pytest = "*"

[packages]
requests = "*"

[requires]
python_version = "3.7"

And a very simple .gitlab-ci.yml file:

image: peque/python-devel

before_script:
  - pipenv sync --dev

python36:
  script:
    - pipenv run pytest

There is also the autogenerated Pipfile.lock file. Which I will not paste here as it is not very interesting.

Now, the problem is Gitlab seems to get blocked when calling pipenv sync:

https://gitlab.com/PequeX/deleteme/-/jobs/171273142

There is no output printed on the log and no error. It just gets blocked forever. And then, eventually, it timeouts (because Gitlab would not let you run a pipeline forever).

@Peque
Copy link
Author

Peque commented Mar 4, 2019

Maybe related: #3534

Will try that workaround.

@Peque
Copy link
Author

Peque commented Mar 4, 2019

It seems the workaround in #3534 does avoid the block at pipenv sync.

@techalchemy
Copy link
Member

Closing -- see #3534 for more info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants