Training and Learning Suite (TLS): Failed to run docker containers after installation

huang06 — Thu, 06 May 2021 10:36:21 GMT

Software: Edge_Insights_for_Industrial_2.3.2
OS: Ubuntu 18.04.5 LTS

I follow the instructions of README.md and install tls-related images, but I fail to run all the tls containers.
Following are the logs of the exited containers.

$ sudo docker-compose ps

    Name                  Command               State                                                          Ports                                                      
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
tls_apiui      ./webservices/start.sh           Exit 0                                                                                                                    
tls_core       ./start.sh                       Up                                                                                                                        
tls_mongo      docker-entrypoint.sh --ssl ...   Up       127.0.0.1:27017->27017/tcp                                                                                       
tls_openvino   /bin/bash                        Exit 0                                                                                                                    
tls_proxy      /docker-entrypoint.sh /bin ...   Exit 0                                                                                                                    
tls_rabbitmq   docker-entrypoint.sh /init ...   Up       0.0.0.0:15672->15672/tcp, 0.0.0.0:1883->1883/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp, 0.0.0.0:8883->8883/tcp
tls_redis      docker-entrypoint.sh sh st ...   Up       127.0.0.1:6379->6379/tcp

$ sudo docker-compose logs tls_apiui

Attaching to tls_apiui
tls_apiui       | wait-for-it.sh: waiting for tls_mongo:27017 without a timeout
tls_apiui       | wait-for-it.sh: tls_mongo:27017 is available after 0 seconds
tls_apiui       | 
tls_apiui       | > tls-ui@2020.6.11 start /home/tls/webservices/ui
tls_apiui       | > node tools/start
tls_apiui       | 
tls_apiui       | 
tls_apiui       | > apiserver@0.0.0 start /home/tls/webservices/apiserver
tls_apiui       | > NODE_ENV=production PRIVATEKEY=rsa.private node app.js --use_strict 
tls_apiui       | 
tls_apiui       | debug: Please note: since `sails.config.session.cookie.secure` is set to `true`, the session cookie 
tls_apiui       | debug: will _only_ be sent over TLS connections (i.e. secure https:// requests).
tls_apiui       | debug: Requests made via http:// will not include a session cookie!
tls_apiui       | debug: 
tls_apiui       | debug: For more help:
tls_apiui       | debug:  • https://sailsjs.com/config/session#?the-secure-flag
tls_apiui       | debug:  • https://sailsjs.com/config/session#?do-i-need-an-ssl-certificate
tls_apiui       | debug:  • https://sailsjs.com/config/sails-config-http#?properties
tls_apiui       | debug:  • https://sailsjs.com/support
tls_apiui       | debug: 
tls_apiui       | Warning: connect.session() MemoryStore is not
tls_apiui       | designed for a production environment, as it will leak
tls_apiui       | memory, and will not scale past a single process.
tls_apiui       | Browserslist: caniuse-lite is outdated. Please run next command `npm update`
tls_apiui       | (node:40) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
tls_apiui       | Starting the development server...
tls_apiui       | error: Bootstrap encountered an error: (see below)
tls_apiui       | error: Failed to lift app: Error: getaddrinfo EAI_AGAIN cvat cvat:8080.
tls_apiui       |     at generateError (/home/tls/webservices/components/cvat/cvat-core/src/server-proxy.js:26:16)
tls_apiui       |     at Object.login (/home/tls/webservices/components/cvat/cvat-core/src/server-proxy.js:158:27)
tls_apiui       |     at process._tickCallback (internal/process/next_tick.js:68:7)
tls_apiui       | 
tls_apiui       | ┌───────────────────────────────────────────────────────┐
tls_apiui       | │                npm update check failed                │
tls_apiui       | │          Try running with sudo or get access          │
tls_apiui       | │         to the local update config store via          │
tls_apiui       | │ sudo chown -R $USER:$(id -gn $USER) /home/tls/.config │
tls_apiui       | └───────────────────────────────────────────────────────┘

$ sudo docker-compose logs tls_openvino

Attaching to tls_openvino

$ sudo docker-compose logs tls_proxy
Attaching to tls_proxy
tls_proxy       | 2020/11/05 08:58:46 [emerg] 11#11: host not found in upstream "cvat" in /etc/nginx/nginx.conf:52
tls_proxy       | nginx: [emerg] host not found in upstream "cvat" in /etc/nginx/nginx.conf:52
tls_proxy       | # Copyright (c) 2020 Intel Corporation.
tls_proxy       | 
tls_proxy       | # Permission is hereby granted, free of charge, to any person obtaining a copy
tls_proxy       | # of this software and associated documentation files (the "Software"), to deal
tls_proxy       | # in the Software without restriction, including without limitation the rights
tls_proxy       | # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
tls_proxy       | # copies of the Software, and to permit persons to whom the Software is
tls_proxy       | # furnished to do so, subject to the following conditions:
tls_proxy       | 
tls_proxy       | # The above copyright notice and this permission notice shall be included in
tls_proxy       | # all copies or substantial portions of the Software.
tls_proxy       | 
tls_proxy       | # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
tls_proxy       | # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
tls_proxy       | # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
tls_proxy       | # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
tls_proxy       | # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
tls_proxy       | # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
tls_proxy       | # SOFTWARE.
tls_proxy       | 
tls_proxy       | worker_processes 4;
tls_proxy       | 
tls_proxy       | events { worker_connections 1024; }
tls_proxy       |  
tls_proxy       | pid        /tmp/nginx.pid;
tls_proxy       | http { 
tls_proxy       |     proxy_buffering off;
tls_proxy       |     client_body_buffer_size 10m;
tls_proxy       |     client_max_body_size    10m;
tls_proxy       | 
tls_proxy       |     client_body_temp_path /tmp/client_temp;
tls_proxy       |     proxy_temp_path       /tmp/proxy_temp_path;
tls_proxy       |     fastcgi_temp_path     /tmp/fastcgi_temp;
tls_proxy       |     uwsgi_temp_path       /tmp/uwsgi_temp;
tls_proxy       |     scgi_temp_path        /tmp/scgi_temp;
tls_proxy       | 
tls_proxy       |     limit_req_zone $request_uri zone=by_uri:10m rate=30r/m;
tls_proxy       | 
tls_proxy       |     server {
tls_proxy       |         listen 443 ssl;
tls_proxy       | 
tls_proxy       |         add_header X-Content-Type-Options "nosniff";
tls_proxy       |         
tls_proxy       |         ssl_certificate /run/secrets/tlsserver_cert;
tls_proxy       |         ssl_certificate_key /run/secrets/tlsserver_key;
tls_proxy       |                         
tls_proxy       |         ssl_session_cache shared:SSL:30m;
tls_proxy       |         ssl_session_timeout 30m;
tls_proxy       |         ssl_session_tickets on; 
tls_proxy       | 
tls_proxy       |         location /cvatapi/ {
tls_proxy       |             proxy_pass http://cvat:8080/;
tls_proxy       |             proxy_pass_header       X-CSRFToken;
tls_proxy       |             proxy_set_header        Host $http_host;
tls_proxy       |             proxy_pass_header       Set-Cookie;
tls_proxy       | 
tls_proxy       |             proxy_set_header Accept-Encoding "";
tls_proxy       |             sub_filter_types *;
tls_proxy       |             sub_filter /static/ /cvatapi/static/;
tls_proxy       |             sub_filter "/static/" "/cvatapi/static/";
tls_proxy       |             sub_filter "/dextr" "/cvatapi/dextr";
tls_proxy       |             sub_filter /api /cvatapi/api;
tls_proxy       |             sub_filter_once off;
tls_proxy       |         }
tls_proxy       | 
tls_proxy       |         location /api/v1 {
tls_proxy       |             proxy_pass http://cvat:8080;
tls_proxy       |             proxy_http_version 1.1;
tls_proxy       |             proxy_set_header Upgrade $http_upgrade;
tls_proxy       |             proxy_set_header Connection "Upgrade";
tls_proxy       |             proxy_set_header Host $host;
tls_proxy       |             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
tls_proxy       |             proxy_set_header X-Forwarded-Proto $scheme;
tls_proxy       |         }
tls_proxy       | 
tls_proxy       |         location /socket.io/ {
tls_proxy       |             proxy_pass https://tls_apiui:1337/socket.io/;
tls_proxy       |             proxy_http_version 1.1;
tls_proxy       |             proxy_set_header Upgrade $http_upgrade;
tls_proxy       |             proxy_set_header Connection "Upgrade";
tls_proxy       |             proxy_set_header Host $host;
tls_proxy       |             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
tls_proxy       |             proxy_set_header X-Forwarded-Proto $scheme;
tls_proxy       |         }
tls_proxy       | 
tls_proxy       |         location /api/ {
tls_proxy       |             proxy_pass https://tls_apiui:1337/api/;
tls_proxy       |             proxy_http_version 1.1;
tls_proxy       |             proxy_set_header Upgrade $http_upgrade;
tls_proxy       |             proxy_set_header Connection "Upgrade";
tls_proxy       |             proxy_set_header Host $host;
tls_proxy       |             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
tls_proxy       |             proxy_set_header X-Forwarded-Proto $scheme;
tls_proxy       |         }
tls_proxy       |                 
tls_proxy       |          location / {
tls_proxy       |             proxy_pass http://tls_apiui:3000/;
tls_proxy       |             proxy_http_version 1.1;
tls_proxy       |             proxy_set_header Upgrade $http_upgrade;
tls_proxy       |             proxy_set_header Connection "Upgrade";
tls_proxy       |             proxy_set_header Host $host;
tls_proxy       |             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
tls_proxy       |             proxy_set_header X-Forwarded-Proto $scheme;
tls_proxy       |         }
tls_proxy       |     }

Re: Training and Learning Suite (TLS): Failed to run docker containers after installation

ChoonHwa — Mon, 30 Nov 2020 02:16:40 GMT

Hi @huang06 ,

In order to make the TLS2.0 running, there need to have 11 containers up and running. They are

tls_proxy, Tls_core, tls_apiui, tls_rabbitmq, tls_redis, tls_mongo, cvat_proxy, cvat_ui, cvat, cvat_db, cvat_redis.

You can invoke $ docker ps to check the container list.

May I know

Was this the first time and fresh environment TLS2.0 installation? If it was setup the TLS application before, may I know did you execute below script before rerun the $ ./setup_TLS_docker.sh
- $ ./cleanup_docker.sh
- $ ./cleanup.sh
Were you using sudoer to run the installation script?

topic Re: Training and Learning Suite (TLS): Failed to run docker containers after installation in Edge Software Catalog

Training and Learning Suite (TLS): Failed to run docker containers after installation

Re: Training and Learning Suite (TLS): Failed to run docker containers after installation