[go: nahoru, domu]

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

Link broken releases.opencti.io #91

Closed
makakin opened this issue Jun 30, 2019 · 4 comments
Closed

Link broken releases.opencti.io #91

makakin opened this issue Jun 30, 2019 · 4 comments
Assignees
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@makakin
Copy link
makakin commented Jun 30, 2019

Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.

Description

Error Msg when init the docker on the first time:
Resolving releases.opencti.io (releases.opencti.io)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'releases.opencti.io'

Environment

  1. OS (where OpenCTI server runs): {CoreOS 2135.4.0}
  2. OpenCTI version: {7f3bd87 }
  3. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:
./docker-compose up

Actual Output

Removing intermediate container 2745352225bc
---> 97c58597263d
Step 6/11 : RUN wget -O /opt/opencti.tar.gz https://releases.opencti.io/opencti-20190626.tar.gz
---> Running in 2faa602d26c9
--2019-06-30 03:07:45-- https://releases.opencti.io/opencti-20190626.tar.gz
Resolving releases.opencti.io (releases.opencti.io)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'releases.opencti.io'
ERROR: Service 'opencti' failed to build: The command '/bin/sh -c wget -O /opt/opencti.tar.gz https://releases.opencti.io/opencti-20190626.tar.gz' returned a non-zero code: 4

@SamuelHassine
Copy link
Member

@makakin Thanks a lot for your bug report. The infrastructure behind releases.opencti.io has suffered a down-time this night. This is now solved so you can run the docker-compose without any problem. Could you please confirm that you do not have this problem anymore?

@richard-julien
Copy link
Member

@SamuelHassine why using a dedicated infra for hosting releases? Github should be a better alternative to fetch the release.

@SamuelHassine SamuelHassine self-assigned this Jun 30, 2019
@SamuelHassine
Copy link
Member

@richard-julien Yes I think so, it was for the time we do not have any release on Github. I will change this on the next version.

@SamuelHassine SamuelHassine added feature use for describing a new feature to develop build and removed feature use for describing a new feature to develop labels Jun 30, 2019
@SamuelHassine SamuelHassine added this to the Release 1.0.1 milestone Jun 30, 2019
@SamuelHassine
Copy link
Member

All Dockerfile are now configured to download the release on Github.

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants