dbdeployer config show

Internal values:

{
"version": "1.17.0",
"sandbox-home": "$HOME/sandboxes",
"sandbox-binary": "$HOME/opt/mysql",
"use-sandbox-catalog": true,
"log-sb-operations": false,
"log-directory": "/home/martin/sandboxes/logs",
"master-slave-base-port": 11000,
"group-replication-base-port": 12000,
"group-replication-sp-base-port": 13000,
"fan-in-replication-base-port": 14000,
"all-masters-replication-base-port": 15000,
"multiple-base-port": 16000,
"group-port-delta": 125,
"mysqlx-port-delta": 10000,
"master-name": "master",
"master-abbr": "m",
"node-prefix": "node",
"slave-prefix": "slave",
"slave-abbr": "s",
"sandbox-prefix": "msb_",
"master-slave-prefix": "rsandbox_",
"group-prefix": "group_msb_",
"group-sp-prefix": "group_sp_msb_",
"multiple-prefix": "multi_msb_",
"fan-in-prefix": "fan_in_msb_",
"all-masters-prefix": "all_masters_msb_",
"reserved-ports": [
1186,
3306,
33060
],
"remote-repository": "https://raw.githubusercontent.com/datacharmer/mysql-docker-minimal/master/dbdata",
"remote-index-file": "available.json",
"timestamp": "Wed Jan 23 16:57:16 EET 2019"
}

from dbdeployer.

I deleted the empty file
/home/martin/.dbdeployer/sandboxes.json

and the error is gone now so closing the issue.

from dbdeployer.

Thanks for your report.
I am able to reproduce it, and I think I understand what the problem could be.

First off, the sandbox is installed, despite what the error message says. The failure occurs while dbdeployer attempts to register the sandbox in the central catalog.

Try running $HOME/sandboxes/msb_8_0_14/use and it should access the database.
(CORRECTION: The sandbox is installed but not activated. The script above won't work)

The error refers to an empty file that should be ignored or treated like an empty JSON structure, but apparently I made a mistake somewhere. The workaround that you have identified is effective. I will code a fix as soon as possible.

from dbdeployer.

Fixed in release 1.17.1

from dbdeployer.