Skip to content

Unable to do pip-sync #853

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
iamMohamed opened this issue Jul 20, 2023 · 5 comments
Closed

Unable to do pip-sync #853

iamMohamed opened this issue Jul 20, 2023 · 5 comments

Comments

@iamMohamed
Copy link

iamMohamed commented Jul 20, 2023

We ran our project in ECS and using ECR

Last month the build was a success but yesterday I triggered the build I got the below error, I made some research on this but I am unable to find the issue.
It's is helpful if I got some guidance.

#11 11.52 OK: 1157 MiB in 92 packages

263 | #11 11.86 Traceback (most recent call last):
264 | #11 11.86 File "/usr/local/bin/pip-sync", line 5, in
265 | #11 11.86 from piptools.scripts.sync import cli
266 | #11 11.86 File "/usr/local/lib/python3.9/site-packages/piptools/scripts/sync.py", line 17, in
267 | #11 11.86 from .. import sync
268 | #11 11.86 File "/usr/local/lib/python3.9/site-packages/piptools/sync.py", line 11, in
269 | #11 11.86 from pip._internal.commands.freeze import DEV_PKGS
270 | #11 11.86 ImportError: cannot import name 'DEV_PKGS' from 'pip._internal.commands.freeze' (/usr/local/lib/python3.9/site-packages/pip/_internal/commands/freeze.py)
271 | #11 ERROR: executor failed running [/bin/sh -c pip install "pip-tools<7.0" && apk add --no-cache --virtual .build-deps build-base cargo git jpeg-dev libffi-dev libxslt-dev postgresql-dev && pip-sync && apk del .build-deps && pip uninstall -y pip-tools]: exit code: 1
272 | ------
273 | > [ 5/10] RUN pip install "pip-tools<7.0" && apk add --no-cache --virtual .build-deps build-base cargo git jpeg-dev libffi-dev libxslt-dev postgresql-dev && pip-sync && apk del .build-deps && pip uninstall -y pip-tools:
274 | ------
275 | executor failed running [/bin/sh -c pip install "pip-tools<7.0" && apk add --no-cache --virtual .build-deps build-base cargo git jpeg-dev libffi-dev libxslt-dev postgresql-dev && pip-sync && apk del .build-deps && pip uninstall -y pip-tools]: exit code: 1
276 |  
277 | [Container] 2023/07/18 13:11:25 Command did not exit successfully DOCKER_BUILDKIT=1 docker build --build-arg DJANGO_SENTRY_RELEASE="$IMAGE_TAG" --file Dockerfile.aws --progress=plain --cache-from $IMAGE_URI:latest --tag "$IMAGE_URI":"$IMAGE_TAG" .
278 | exit status 1
279 | [Container] 2023/07/18 13:11:25 Phase complete: BUILD State: FAILED_WITH_ABORT
280 | [Container] 2023/07/18 13:11:25 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: DOCKER_BUILDKIT=1 docker build --build-arg DJANGO_SENTRY_RELEASE="$IMAGE_TAG" --file Dockerfile.aws --progress=plain --cache-from $IMAGE_URI:latest --tag "$IMAGE_URI":"$IMAGE_TAG" .
281 | . Reason: exit status 1
282 |  

@tianon
Copy link
Member

tianon commented Jul 20, 2023

I don't know what pip-sync is, but I don't think it's something we include in the image, right? 😅

(The error message there sounds like this is something going wrong in pip-sync itself)

It's possible this is related to #835 (and friends) and is thus libseccomp related (proper fix being to update libseccomp2, runc, and Docker on your host, workaround being to switch to the -bullseye images explicitly), but I would've thought it'd fail sooner in that case.

@iamMohamed
Copy link
Author

Hello @tianon I appreciate your thought, I thought that any batch update from the image side would cause the issue because it worked fine last week.
Thanks.

@ad-m-ss
Copy link

ad-m-ss commented Oct 10, 2023

We may update pip version, but this is still an issue of pip-sync of compatibility with official pip version. You can use virtualenv to downgrade & pin pip in the container if you need specific version.

@ad-m-ss
Copy link

ad-m-ss commented Oct 10, 2023

@yosifkit
Copy link
Member

Thanks for checking @ad-m-ss. I'll go ahead and close since it is fixed in the pip-tools package.

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

4 participants