Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker image failing (exited with code 132) #4602

Closed
kahekahe opened this issue Oct 12, 2019 · 14 comments
Closed

docker image failing (exited with code 132) #4602

kahekahe opened this issue Oct 12, 2019 · 14 comments
Labels
status:stale type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@kahekahe
Copy link

Rasa version: 1.3.9

Python version: 3.6

Operating system (windows, osx, …): Ubuntu 18.04 (Docker version: 19.03.3 / linux/amd64) Docker-compose version 3.0

Issue:

trying to run the latest docker image rasa/rasa:latest on a linux machine (using docker-compose), but I'm getting rasa-test_rasa-svc_1 exited with code 132

Error (including full traceback):

Creating rasa-test_rasa-svc_1 ... done
compose.parallel.feed_queue: Pending: set()
compose.parallel.parallel_execute_iter: Finished processing: <Service: rasa-svc>
compose.parallel.feed_queue: Pending: set()
Attaching to rasa-test_rasa-svc_1
compose.cli.verbose_proxy.proxy_callable: docker events <- (filters={'label': ['com.docker.compose.project=rasa-test', 'com.docker.compose.oneoff=False']}, deco
de=True)
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.25/events?filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Drasa-test%22%2C+%22c
om.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker events -> <docker.types.daemon.CancellableStream object at 0x7f0a342c2470>
compose.cli.verbose_proxy.proxy_callable: docker wait <- ('7264cf5b2a1aa971da4e82e475865a3dacbd0a434ff88aedb377717a2522ee4a')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('7264cf5b2a1aa971da4e82e475865a3dacbd0a434ff88aedb377717a2522ee4a')
urllib3.connectionpool._make_request: http://localhost:None "POST /v1.25/containers/7264cf5b2a1aa971da4e82e475865a3dacbd0a434ff88aedb377717a2522ee4a/wait HTTP/
1.1" 200 32
compose.cli.verbose_proxy.proxy_callable: docker wait -> {'Error': None, 'StatusCode': 132}
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.25/containers/7264cf5b2a1aa971da4e82e475865a3dacbd0a434ff88aedb377717a2522ee4a/json HTTP/1
.1" 200 None
rasa-test_rasa-svc_1 exited with code 132
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
 'Args': ['run', '--enable-api', '--cors', '*'],
 'Config': {'AttachStderr': False,
            'AttachStdin': False,
            'AttachStdout': False,
            'Cmd': ['run', '--enable-api', '--cors', '*'],
            'Domainname': '',
            'Entrypoint': ['rasa'],
            'Env': ['PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
                    'LANG=C.UTF-8',

Command or request that led to error:

docker-compose --verbose up

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

@kahekahe kahekahe added the type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors. label Oct 12, 2019
@sara-tagger
Copy link
Collaborator

Thanks for the issue, @imLew will get back to you about it soon!

You may find help in the docs and the forum, too 🤗

@imLew
Copy link
Contributor

imLew commented Oct 15, 2019

Could you please post the contents of your docker-compose.yml?

@kahekahe
Copy link
Author

version: '3.0'
services:
  rasa-svc:
    build: ./svc
    image: rasa/rasa:latest
    ports:
      - 5005:5005
      - 5006:5006
      - 5002:5002
    volumes:
      - ./app:/app
    command:
       - run
       - --enable-api
       - --cors
       - "*"
    user: root

@imLew
Copy link
Contributor

imLew commented Oct 25, 2019

@kahekahe sorry for not getting back to you soon. Do you still have this problem?

@stale
Copy link

stale bot commented Jan 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status:stale label Jan 24, 2020
@stale
Copy link

stale bot commented Jan 31, 2020

This issue has been automatically closed due to inactivity. Please create a new issue if you need more help.

@stale stale bot closed this as completed Jan 31, 2020
@ThWoywod
Copy link

ThWoywod commented May 7, 2020

Does somebody have any solution for this issue?
I have this problem myself on a server with an a bit old virtualized CPU.

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 6
model name	: Common KVM processor
stepping	: 1
microcode	: 0x1
cpu MHz		: 2493.788
cache size	: 16384 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology pni cx16 x2apic hypervisor lahf_lm kaiser
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips	: 4987.57
clflush size	: 64
cache_alignment	: 128
address sizes	: 40 bits physical, 48 bits virtual
power management:

I run this command: docker run -p 5005:5005 -ti rasa/rasa:1.9.5 run -m models --enable-api

@saurabhchandrapatel
Copy link

I am also getting the same issue

@ThWoywod
Copy link

@saurabhchandrapatel in my case it was Tensorflow that returns this error code.
The default Tensorflow build was not been able to run on old CPUs that does not support AVX instructions. https://www.tensorflow.org/install/pip#hardware-requirements

I solved this issue by build my own Tensorflow Wheel without AVX instructions and create my own Rasa Image.

@h4de5
Copy link

h4de5 commented Dec 1, 2020

@ThWoywod can you explain how you did this?

@cespinoza-dev
Copy link

I have the same problem using when i tried to run a mongo docker image in my laptop:
"Intel® Core™ i5 CPU M 460 @ 2.53GHz × 4"
OS: Ubuntu 20.04.2 LTS
@ThWoywod could you explain us how did you create a new image to resolve this issue? thanks in advance

@bharath-kumarn
Copy link

app_1 | Use a production WSGI server instead.
app_1 | * Debug mode: off
app_1 | * Environment: production
app_1 | WARNING: This is a development server. Do not use it in a production deployment.
app_1 | Use a production WSGI server instead.
app_1 | * Debug mode: off

imageai_object_detection_app_1 exited with code 132

@wintermute23
Copy link

wintermute23 commented Aug 9, 2021

Had the same Error here with a custom Dockerfile.

I used

ENV PHP_CFLAGS="-march=native -fstack-protector-strong -fpic -fpie -O3 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
ENV PHP_CPPFLAGS="$PHP_CFLAGS"

in Dockerfile, I changed the CPU of the host System, then I got Error 132.

This solved the Problem for me:

Rebuild the whole Image with:
docker-compose build --no-cache

After that, run:
docker-compose up -d

and you should be fine.

Edit: typos

@mattiadevivo
Copy link

I had the same problem using a Docker image built on a different machine.

I solved by rebuilding the image on the destination host like @wintermute23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:stale type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

10 participants