question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docker image failing (exited with code 132)

See original GitHub issue

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):


Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
ThWoywodcommented, Aug 28, 2020

@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.

1reaction
wintermute23commented, 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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Docker container exited with code 132 - General Discussions
When I ran the mongo container on server A with OS Ubuntu 20.04Lts, it's been always exited with code 132. however, I can...
Read more >
1795574 – Many base docker images fail with code 132 ...
We see the error message "docker exited with code 132" when we try to run or bash into the container. When we did...
Read more >
ERROR: Job failed: exit code 132 - gitlab-runner
When I try to run the image directly in docker, it fails. Docker commands: docker run -d --name cakephp-72 302dev/cakephp:7.2-cli; docker run -t ......
Read more >
Docker Exited (132) - Medium
I had tried to prove a problem from the Kong API docker container. Issue an error code 132 when running the migration command....
Read more >
[Solved]-Docker containers exit code 132-docker
Step 2: To solve the problem, run an image built to support amd64 and not amd64-avx this may mean you have to run...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found