intrigue core not running in ubuntu 20 wsl 2 win10
maddy45 opened this issue · 3 comments
Not able to run intrigue-core in windows 10 from Docker Desktop and also from wsl 2 ubuntu 20
Here is the output of my command,
mad@DESKTOP-DQBF7IL:~$ docker pull $IMAGE && \
docker run -e LANG=C.UTF-8
--memory=8g
-v ~/intrigue-core-data:/data
-p 0.0.0.0:7777:7777
-it $IMAGE
latest: Pulling from intrigueio/intrigue-core
Digest: sha256:3521659d8e009b0dae48422119811a8ba353d927cea63cf9e7cf18a076916458
Status: Image is up to date for intrigueio/intrigue-core:latest
docker.io/intrigueio/intrigue-core:latest
//
/ Welcome to Intrigue Core! /
/ /
/ Please file bugs & requests here: https://github.com/intrigueio/intrigue-core/issues /
/ /
/ Other comments? Questions? Email hello@intrigue.io. /
//
[+] Configuing postgres
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
[+] Starting postgres
- Starting PostgreSQL 12 database server [ OK ]
[+] Starting redis
Starting redis-server: redis-server.
[+] Migrating DB for Intrigue Standalone
[+] Schema Version: 66
[+] Setting up Intrigue Standalone
[+] Setup initiated!
[+] Copying Procfile....
[ ] File already exists, skipping: /core/Procfile
[+] Copying puma config....
[ ] File already exists, skipping: /core/config/puma.rb
[+] Copying system config....
[+] Creating system config: /core/config/config.json
[+] GENERATING NEW SYSTEM PASSWORD!
[+] GENERATING NEW SYSTEM API KEY!
[+] SSL Certificate exists...
[+] Copying database config.
[ ] File already exists, skipping: /core/config/database.yml
[+] Copying redis config.
[ ] File already exists, skipping: /core/config/redis.yml
[+] Setting up sidekiq config....
[+] /core/config/sidekiq.yml already exists!
[+] Downloading latest data files...
gzip: nvdcve-1.0-2019.json.gz: unexpected end of file
gzip: nvdcve-1.0-2018.json.gz: unexpected end of file
gzip: nvdcve-1.0-2017.json.gz: unexpected end of file
[+] Getting latest web_accounts_list.json
[+] Getting latest ipv4-address-space.csv
[+] Getting latest tcp / udp port numbers
[+] Getting latest Public suffix list
[ ] Cleaning NVD directory
[+] Getting latest NVD JSON Feed: 2019
[+] Getting latest NVD JSON Feed: 2018
[+] Getting latest NVD JSON Feed: 2017
[+] Data Update Complete!
[+] ===================================
[+] SYSTEM USERNAME: intrigue
[+] SYSTEM PASSWORD: evwprulmqfu
[+] ===================================
[+] Complete!
[+] Enabling Intrigue Services
god[732]: Syslog enabled.
god[1087]: Loading /core/util/god/intrigue-docker.rb
god[1087]: Using pid file directory: /core/tmp/pids
Sending 'start' command
The following watches were affected:
intrigue-web
intrigue-worker
intrigue-resolver
intrigue-chrome
intrigue-tika
[+] Tailing worker log
Redis#exists(key)
will return an Integer by default in redis-rb 4.3. The option to explicitly disable this behaviour via Redis.exists_returns_integer
will be removed in 5.0. You should use exists?
instead.
Connecting to Redis Server at: redis://127.0.0.1:6379/
2020-10-09T07:06:28.072Z pid=1318 tid=gsjr7bdla INFO: Booting Sidekiq 6.1.2 with redis options {:url=>"redis://127.0.0.1:6379/"}
/core/lib/tasks/uri_check_subdomain_hijack.rb:72: warning: regex literal in condition
Sourcing intrigue issues from /core/lib
2020-10-09T07:06:54.393Z pid=1318 tid=gsjr7bdla INFO: Running in ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]
2020-10-09T07:06:54.393Z pid=1318 tid=gsjr7bdla INFO: See LICENSE and the LGPL-3.0 for licensing details.
2020-10-09T07:06:54.393Z pid=1318 tid=gsjr7bdla INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
2020-10-09T07:06:54.395Z pid=1318 tid=gsjr7bdla DEBUG: Client Middleware:
2020-10-09T07:06:54.395Z pid=1318 tid=gsjr7bdla DEBUG: Server Middleware:
2020-10-09T07:06:54.395Z pid=1318 tid=gsjr7bdla DEBUG: {:queues=>["default"], :labels=>[], :concurrency=>60, :require=>"/core/core.rb", :strict=>true, :environment=>nil, :timeout=>25, :poll_interval_average=>nil, :average_scheduled_poll_interval=>5, :error_handlers=>[#Sidekiq::ExceptionHandler::Logger:0x0000562caff9e8e0], :death_handlers=>[], :lifecycle_events=>{:startup=>[], :quiet=>[], :shutdown=>[], :heartbeat=>[]}, :dead_max_jobs=>10000, :dead_timeout_in_seconds=>15552000, :reloader=>#Proc:0x0000562cafef0e20@/root/.rbenv/versions/2.6.5/gemsets/core/gems/sidekiq-6.1.2/lib/sidekiq.rb:38, :verbose=>true, :dynamic=>true, :process_limits=>{:task=>5, :control=>1, :task_enrichment=>20, :task_browser=>1, :task_autoscheduled=>20, :task_scan=>3, :task_spider=>3, :app=>3, :graph=>1}, :config_file=>"/core/config/sidekiq.yml", :identity=>"4e46309d3894:1318:b90cefc6a092", :fetch=>Sidekiq::LimitFetch}
That looks like it's running. What happens when you try to connect to https://127.0.0.1:7777/ in your browser?
Yeah you might have found some references to http on 7777, we changed this default a couple releases back. If you're still having trouble, feel free to join us in #core-help in the slack chan... you can sign up here: http://core.intrigue.io/2020/06/21/opening-up-the-community/
Closing this out, thanks @JoeUser47 for the quick insight!
not getting anything on 7777, it is replying ' the site can't be reached '