Troubleshooting

We are striving to make sure you do not encounter any issues while installing or using FontoXML Content Quality. However, since we are all humans, you might encounter an issue that we could not (yet) prevent.

This page tries to describe a path forward on issues you encounter. If you do not find a solution for your problem, please do not hesitate to ask us for a solution!

Running using the fdt fcq command

Couldn't connect to Docker daemon (Linux only)

fontoxml@fdt-fcq-test-vm:~/fcq$ fdt fcq run

  You're not running from inside an editor repository; this means this tool may not work as expected!

  fdt fcq run
  Building instance

  Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

  If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

  Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

  If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

  Building dev image at "/home/fontoxml/fcq"... (812ms)

  failure
  docker-compose down exited with code 1
    Error: docker-compose down exited with code 1
    at ChildProcess.childProcess.on.code (/usr/lib/node_modules/@fontoxml/fontoxml-development-tools/node_modules/@fontoxml/fontoxml-development-tools-module-fcq/src/utilities/executeAndLog.js:42:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
  cwd   /home/fontoxml/fcq
  args  fdt fcq run
  mods  fotno-module-core (1.0.0)
        @fontoxml/fontoxml-development-tools-module-connectors (2.1.0)
        @fontoxml/fontoxml-development-tools-module-core (1.1.1)
        @fontoxml/fontoxml-development-tools-module-fcq (1.0.1)
        @fontoxml/fontoxml-development-tools-module-localization (2.0.0)
        @fontoxml/fontoxml-development-tools-module-operations (1.1.0)
        @fontoxml/fontoxml-development-tools-module-schema (1.1.0)

Cause: The user does not have access to the Unix socket to which Docker is bound.

Solution: Run the Docker post-installation steps for Linux. Specifically the steps regarding adding the user to the docker group.

Error loading config file ... permission denied (Linux only)

fontoxml@fdt-fcq-test-vm:~/fcq$ fdt fcq build

  You're not running from inside an editor repository; this means this tool may not work as expected!

  fdt fcq build  
  WARNING: Error loading config file: /home/fontoxml/.docker/config.json: stat /home/fontoxml/.docker/config.json: permission denied  

  Get https://fontoxmlsdk.azurecr.io/v2/fontoxml/fcq/fcq-sdk/manifests/1.2.0: unauthorized: authentication required  

  Removing temporary resources... (2ms)  
  Building the production image "fontoxml/fcq/fcq-instance:latest" at "/home/fontoxml/fcq"... (367ms)  

  failure  
  docker build -t fontoxml/fcq/fcq-instance:latest . exited with code 1  
    Error: docker build -t fontoxml/fcq/fcq-instance:latest . exited with code 1  
    at ChildProcess.childProcess.on.code  
    (/home/fontoxml/.nvm/versions/node/v8.11.3/lib/node_modules/@fontoxml/fontoxml-development-tools/node_modules/@fontoxml/fontoxml-development-tools-module-fcq/src/utilities/executeAndLog.js:42:12)  
    at emitTwo (events.js:126:13)  
    at ChildProcess.emit (events.js:214:7)  
    at maybeClose (internal/child_process.js:925:16)  
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)  
  cwd   /home/fontoxml/fcq
  args  fdt fcq build
  mods  fotno-module-core (1.0.0)
        @fontoxml/fontoxml-development-tools-module-connectors (2.1.0)
        @fontoxml/fontoxml-development-tools-module-core (1.1.1)
        @fontoxml/fontoxml-development-tools-module-fcq (1.0.1)
        @fontoxml/fontoxml-development-tools-module-localization (2.0.0)
        @fontoxml/fontoxml-development-tools-module-operations (1.1.0)
        @fontoxml/fontoxml-development-tools-module-schema (1.1.0)

Cause: The user does not have access to the Unix socket to which Docker is bound.

Solution: Run the Docker post-installation steps for Linux. Specifically the steps regarding the ~/.docker directory, either by fixing the permissions or removing it entirely.