0 votes
1 view

Hey community, 

After installing knowage as a docker instance following the steps mentioned on github (here), I receive permanent error messages saying that knowage cannot connect to MySQL. Basically, I downloaded the docker-compose file and ran it using docker-compose up. This is how it looks like in powershell: 

PS C:\fiware> docker-compose up
Starting fiware_knowagedb_1 ... done
Starting fiware_knowage_1   ... done
Attaching to fiware_knowagedb_1, fiware_knowage_1
knowagedb_1  | 190327  9:41:01 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
knowagedb_1  | 190327  9:41:01 [Note] mysqld (mysqld 5.5.62) starting as process 1 ...
knowagedb_1  | 190327  9:41:01 [Note] Plugin 'FEDERATED' is disabled.
knowagedb_1  | 190327  9:41:01 InnoDB: The InnoDB memory heap is disabled
knowagedb_1  | 190327  9:41:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
knowagedb_1  | 190327  9:41:01 InnoDB: Compressed tables use zlib 1.2.11
knowagedb_1  | 190327  9:41:01 InnoDB: Using Linux native AIO
knowagedb_1  | 190327  9:41:01 InnoDB: Initializing buffer pool, size = 128.0M
knowagedb_1  | 190327  9:41:01 InnoDB: Completed initialization of buffer pool
knowagedb_1  | 190327  9:41:01 InnoDB: highest supported file format is Barracuda.
knowagedb_1  | 190327  9:41:02  InnoDB: Waiting for the background threads to start
knowagedb_1  | 190327  9:41:03 InnoDB: 5.5.62 started; log sequence number 1595675
knowagedb_1  | 190327  9:41:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
knowagedb_1  | 190327  9:41:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
knowagedb_1  | 190327  9:41:03 [Note] Server socket created on IP: '0.0.0.0'.
knowagedb_1  | 190327  9:41:03 [Warning] 'proxies_priv' entry '@ root@b40492ee2a04' ignored in --skip-name-resolve mode.
knowagedb_1  | 190327  9:41:03 [Note] Event Scheduler: Loaded 0 events
knowagedb_1  | 190327  9:41:03 [Note] mysqld: ready for connections.
knowagedb_1  | Version: '5.5.62'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
knowage_1    |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
knowage_1    |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host:
knowage_1    | Wed Mar 27 09:41:10 UTC 2019 - still trying to connect to mysql
knowage_1    |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
knowage_1    |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host:
knowage_1    | Wed Mar 27 09:41:11 UTC 2019 - still trying to connect to mysql
knowage_1    |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
knowage_1    |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host:
knowage_1    | Wed Mar 27 09:41:12 UTC 2019 - still trying to connect to mysql
Gracefully stopping... (press Ctrl+C again to force)
Stopping fiware_knowage_1   ...
Stopping fiware_knowagedb_1 ...

Does anybody know why the pre-defined docker-compose file do not work on my Windows 10 machine? 

Thanks for all hints, 
Kevin 

Environment knowagelabs/knowage-server-docker:6.2.2; Windows 10; Docker Engine - Community Version: 18.09.1
asked Mar 30, 2019 in Docker by kevin (360 points) | 1 view

Please log in or register to answer this question.

1,553 questions
1,017 answers
2,037 comments
2,567 users