compreface-core exits with code 132 during startup
See original GitHub issueDescribe the bug Running on ubuntu 18.04 with docker following docker compose container exits with error code 132
To Reproduce Steps to reproduce the behavior: Followed 0.4.1 release instructions
Expected behavior It should start
Desktop (please complete the following information):
- OS: 18.04 Ubuntu
- Browser: chrome
- Version: 0.4.1
Additional context
[uWSGI] getting INI configuration from uwsgi.ini
*** Starting uWSGI 2.0.18 (64bit) on [Thu Feb 25 15:48:21 2021] ***
compiled with version: 8.3.0 on 20 January 2021 11:36:38
os: Linux-4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021
nodename: 425a88b1bf62
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /app/ml
detected binary path: /usr/local/bin/uwsgi
setgid() to 33
setuid() to 33
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 0.0.0.0:3000 fd 3
Python version: 3.7.4 (default, Sep 12 2019, 15:40:15) [GCC 8.3.0]
Python main interpreter initialized at 0x562db793dff0
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 145840 bytes (142 KB) for 1 cores
*** Operational MODE: single process ***
[uWSGI] getting INI configuration from uwsgi.ini
*** Starting uWSGI 2.0.18 (64bit) on [Thu Feb 25 16:08:44 2021] ***
compiled with version: 8.3.0 on 20 January 2021 11:36:38
os: Linux-4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021
nodename: 425a88b1bf62
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /app/ml
detected binary path: /usr/local/bin/uwsgi
setgid() to 33
setuid() to 33
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 0.0.0.0:3000 fd 3
Python version: 3.7.4 (default, Sep 12 2019, 15:40:15) [GCC 8.3.0]
Python main interpreter initialized at 0x55d851ac7ff0
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 145840 bytes (142 KB) for 1 cores
*** Operational MODE: single process ***
Issue Analytics
- State:
- Created 3 years ago
- Comments:17
Top Results From Across the Web
Summary - GitLab
Summary. When running a job in gitlab-runner, I'm getting the error: ERROR: Job failed: exit code 132.
Read more >Mongodb immediately exits with error 132, and will not ressurect
I went to start a cloud9 container to make changes to static html files on the server, and noticed that MongoDB exited. I...
Read more >Gstreamer Process finished with exit code 132 on OSX with ...
It is likely due to some requirements related to OpenGL on MacOS. Please note that in your example the playbin will try to...
Read more >Docker container exited with code 132 - General Discussions
Hi, I need your help from all of you guys. When I ran the mongo container on server A with OS Ubuntu 20.04Lts,...
Read more >1795574 – Many base docker images fail with code 132 ...
--> Containers worked fine in-memory but could not be started ever again. We see the error message "docker exited with code 132" when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
looks like this is really the problem of the old CPU: https://github.com/tensorflow/tensorflow/issues/18147#issuecomment-384808914 We removed AVX2 support in our release, so it will work on the old CPUs, but it looks like your CPU even older as it doesn’t support AVX. The thing is it’s difficult to replace the current version of Tensorflow with a version without AVX support, as there is not such version in pip that we use. So, unfortunately, we won’t support it. You can still try to build a version with alternative Tensorflow and share it with the community.
Got it. Thank you!