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

[Connectors] When pulling Splunk docker image after release, context build error #2977

Closed
helene-nguyen opened this issue Nov 18, 2024 · 0 comments · Fixed by #2986
Closed
Assignees
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@helene-nguyen
Copy link
Member

Description

When pulling Splunk docker image after release, context build error

Issue:

/entrypoint.sh: cd: line 4: can't cd to /opt/opencti-connector-qradar: No such file or directory
python3: can't open file '//qradar.py': [Errno 2] No such file or directory

When checking the image:

Image

╰─ docker run -it --rm --entrypoint=sh opencti/connector-splunk:6.3.12
/ # cat entrypoint.sh
#!/bin/sh

# Go to the right directory
cd /opt/opencti-connector-qradar

# Launch the worker
python3 qradar.py
/ #

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

Actual Output

Additional information

Screenshots (optional)

@helene-nguyen helene-nguyen added bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. labels Nov 18, 2024
@helene-nguyen helene-nguyen self-assigned this Nov 18, 2024
@helene-nguyen helene-nguyen added this to the Bugs backlog milestone Nov 18, 2024
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 18, 2024
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 filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. 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