Skip to content
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

[Bambenek] Fix Dockerfile for CI #3511

Closed
helene-nguyen opened this issue Feb 27, 2025 · 0 comments · Fixed by #3512
Closed

[Bambenek] Fix Dockerfile for CI #3511

helene-nguyen opened this issue Feb 27, 2025 · 0 comments · Fixed by #3512
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@helene-nguyen
Copy link
Member

Description

Issue reported when build in CI

 > [3/6] RUN cd /opt/opencti-connector-bambenek &&     pip3 install --no-cache-dir -r requirements.txt &&     apk del git build-base:
#0 0.073 /bin/sh: cd: line 0: can't cd to /opt/opencti-connector-bambenek: No such file or directory
------
Dockerfile:12
--------------------
  11 |     
  12 | >>> RUN cd $SRC_DIR && \
  13 | >>>     pip3 install --no-cache-dir -r requirements.txt && \
  14 | >>>     apk del git build-base
  15 |     
--------------------
error: failed to solve: process "/bin/sh -c cd $SRC_DIR &&     pip3 install --no-cache-dir -r requirements.txt &&     apk del git build-base" did not complete successfully: exit code: 2

Exited with code exit status 1
@helene-nguyen helene-nguyen added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 27, 2025
@helene-nguyen helene-nguyen self-assigned this Feb 27, 2025
@helene-nguyen helene-nguyen removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 27, 2025
@helene-nguyen helene-nguyen added this to the Release 6.5.4 milestone Feb 27, 2025
@helene-nguyen helene-nguyen linked a pull request Feb 27, 2025 that will close this issue
4 tasks
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant