We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

initialize error

Comments

3 comments

  • Avatar
    Brenda Stoetzer

    Hi Chenghao,

    DQ+'s scripts don't make calls to this repo since DQ+ will unpack a pre-configured docker container with Postgres installed. Were the scripts modified to download a separate Postgres repo? If so, it looks like this post would be directly related to this other post. https://support.infogix.com/hc/en-us/community/posts/360037814013-how-to-use-internal-maven-repo-when-initializing

     

    0
    Comment actions Permalink
  • Avatar
    Xiao, Chenghao

    do you have more information about the docker config? currently I always get the error message "Cannot connec tto Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

    and when I try ./startApplication will also get below error message
    > Configure project :
    Auth Type=INTERNAL
    sagacityLoadBalancer#0|:
    Starting new docker container for sagacityLoadBalancer...
    sagacityLoadBalancer#2|Unable to find image 'sagacity/load-balancer:3.1.0' locally
    sagacityLoadBalancer#2|Trying to pull repository registry.access.redhat.com/sagacity/load-balancer ...
    sagacityLoadBalancer#2|Trying to pull repository docker.io/sagacity/load-balancer ...
    sagacityLoadBalancer#2|/usr/bin/docker-current: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
    sagacityLoadBalancer#2|See '/usr/bin/docker-current run --help'.
    Failed command sagacityLoadBalancer#2 with status 125: docker run -p 80:80 -p 443:443 -p 9100-9120:9100-9120 --net=host --name sagacityLoadBalancer --restart unless-stopped -e SAG_UID=$(id -u) -e SAG_GID=$(id -g) -e MOD_CLUSTER_ADMIN_USER=sagacity -e MOD_CLUSTER_ADMIN_PASSWORD=GQSsqe321 -v /etc/localtime:/etc/localtime -v /opt/infogix/data/runtime/apache/conf/ssl:/usr/local/apache2/ssl -d sagacity/load-balancer:3.1.0

    > Task :startLoadBalancer FAILED

    FAILURE: Build failed with an exception.

    0
    Comment actions Permalink
  • Avatar
    Brenda Stoetzer

    Hi Chenghao,

    Following up to confirm the above was resolved along with your connectivity issues related to this post https://support.infogix.com/hc/en-us/community/posts/360037760314-loadbalance-issue,. 

    Also confirming your question above "do you have more information about the docker config" will continue on the ticket we are currently communicating with you on.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.