Skip to main content
Version: ACE 4

Frequently Answered Questions

This page contains answers to Frequently Answered Questions

If you are not able to find answer here, then please ask question in ACE support chat

Errors when starting ACE with docker images built locally​

Problem​

When running docker-compose up. ACE fails tos tart with error similar to:

digital-api-orch_1      | $ rimraf dist && npm run build
': No such file or directoryv: can't execute '/bin/sh

Solution​

Make sure that core.autocrlf is set to input by running:

git config --global core.autocrlf input

Remove affected repositories and clone them again from the remote.

Machine slow and unresponsive when running docker-compose up​

Problem​

By default docker machine is allocated 2GB of RAM.

Solution​

Allocate sufficient amount of memory for docker VM by running:

docker-machine stop
VBoxManage modifyvm default --cpus 2
VBoxManage modifyvm default --memory 4096
docker-machine start

Bash shell not starting from Powershell or Windows Terminal (powershell core)​

Problem​

Installation steps from Getting started guide were performed in native windows Powershell, rather than in Windows terminal (Powershell core)

Solution​

Perform installation steps in Windows Terminal (Powershell Core).

ACE is timing out with HTTP error 504 in Kubernetes environment​

Problem​

Ingress is timing out the requests.

Solution​

Change timeout in ingress definition. See ingress documentation for the additional details.

For example, to set timeout to 10 minutes, add annotations:

    nginx.ingress.kubernetes.io/proxy-connect-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "600"

or in newer versions of ingress controller:

    nginx.org/proxy-connect-timeout: 600s
    nginx.org/proxy-read-timeout: 600s
    nginx.org/proxy-send-timeout: 600s

Requests through ACE are slow​

Problem​

Caching is not enabled

Solution​